https://www.prisma.io/ logo
Join SlackCommunities
Powered by
<@UA3DWCD9B> can you share `docker ps`?
# orm-help
n
@carstenbaumhoegger can you share 
docker ps
?
please use this thread @carstenbaumhoegger
c
Copy code
CONTAINER ID        IMAGE                      COMMAND                  CREATED             STATUS                          PORTS                    NAMES
f8a12b5a0e58        prismagraphql/prisma:1.8   “/bin/sh -c /app/sta…”   5 minutes ago       Restarting (1) 18 seconds ago                            database_prisma_1
67008b954308        prismagraphql/prisma:1.8   “/bin/sh -c /app/sta…”   7 minutes ago       Restarting (1) 26 seconds ago                            local_prisma-database_1
42d9224fc79b        mysql:5.7                  “docker-entrypoint.s…”   7 minutes ago       Up 7 minutes                    0.0.0.0:3307->3306/tcp   prisma-db
n
looks like your Prisma server isn't running
c
I just checked out the boilerplate, edited my 
.env
file (Prisma Cloud is down), used 
docker-compose up -d
to start the containers and then ran 
prisma deploy
n
I also don't know why you have two 
prismagraphql/prisma:1.8
containers there
c
I’ll kill all containers and try again
n
make sure to kill + rm
👍 1
c
alright. I killed the Containers, ran 
docker-compose up -d
again and then 
prisma deploy
. Now I’m getting this error
Copy code
Creating stage dev for service backend !
 ▸    Could not connect to cluster local. Please use docker-compose up -d to start your local Prisma cluster.

Get in touch if you need help: <https://www.graph.cool/forum>
To get more detailed output, run $ export DEBUG="*"
docker ps
shows:
Copy code
CONTAINER ID        IMAGE                      COMMAND                  CREATED             STATUS                          PORTS               NAMES
9edbcde217df        prismagraphql/prisma:1.8   "/bin/sh -c /app/sta…"   32 seconds ago      Restarting (1) 10 seconds ago                       database_prisma_1
Maybe my local link is not correct? 
PRISMA_ENDPOINT="<http://localhost:4466/backend/dev>"
n
Restarting (1) 10
this is not correct, and means your server isn't running
can you share 
docker-compose.yml
?
c
Maybe I put the project in a litte repo and share it with you to reproduce?
n
It might be something about your docker environment, but sharing the repo will definitely help 👌
c
n
ah I see the problem now
your 
docker-compose.yml
doesn't contain information for the Prisma server to which DB it should connect to
run 
prisma init
, then choose 
create new database
in a new folder to see how such a 
docker-compose.yml
could look like 🙂
c
ahh! Alright i didn’t know that running 
prisma init
was still required, when using the boilerplate! Maybe the documentation can be adjusted, so that noone forgets to run that? 😄
n
You are not supposed to run 
prisma init
when using the boilerplates 🙂 but we should definitely think about covering that path better (moving from demo server + DB to local server + DB)
c
great! I generated a fresh 
docker-compose
file and pasted it into the existing project, now everything works fine. Thanks for your time! If you need some help improving the docs, I’m willing to help! 🙂
🎉 1
n
awesome 🙌
I think raising this topic in a new issue here is a good start: https://github.com/graphql-boilerplates/node-graphql-server/! I think this is a topic that goes beyond documentation, the actual concept needs to work differently imo
c
alright, I’m going to open an issue and describe the problem I faced 🙂
🙏 1
should I really open the issue at 
node-graphql-server
or at 
typescript-graphql-server
?
n
either works 😄
c
haha alright 😄
n
thanks Carsten!
c
thanks for all the help! Would love to meet you at GraphQL Europe!
n
sure, let's have a chat then 😄 there's also going to be a workshop the day before
c
alright great! I didn’t know about that and haven’t booked the hotel room, I’d love to attend there! 😄
n
nice, we'll post more about that in #graphql-europe soon 🙂
c
thanks for the info!
Open in Slack
PreviousNext
Powered by