https://www.prisma.io/ logo
Join Slack
Powered by
hello, can someone help? Thank you, much appreciat...
# orm-help
j
hello, can someone help? Thank you, much appreciated.
a
Legacy desktop solution. Docker Toolbox is for older Mac and Windows systems that do not meet the requirements of Docker for Mac and Docker for Windows. We recommend updating to the newer applications, if possible.
Would it be possible for you to just install Docker for Windows instead?
j
@Arnab I am using Windows Home for my laptop so I cannot install Docker for Windows. Mind you, I’ve thought about that even before using Prisma because I’ve been experiencing a lot of errors using Mongo. I can’t switch to Windows 10 Pro yet because of financial reasons.
a
So it sounds to me that the errors you are experiencing are related to docker toolbox in general?
j
Yes but this error is something I only encountered in Prisma.
a
Try inserting this in your docker-compose file under postgres:
Copy code
ports:
  - "5432:5432"
j
Okay will try it once I get home But in my latest thread in the Prisma Forum I excluded postgres image there because it was only something I tried, but was not pre-made upon using prisma cli. Should I put it back, then?
a
Well if you don't include the postgres image in your docker-compose..are you running postgres separately then?
I mean, you can run it outside of docker obviously and expose the ports..I guess.
j
yeah I have postgres locally and that’s what I originally want to try
but it doesn’t work. So I tried running it on Docker in the hopes of getting it to work
a
Were you able to connect to your postgres through say... SQL Pro?
j
I can connect to my postgres through PgAdmin and my own command prompt
a
Strange
Just try the ports thing. See if that works.
n
j
I tried it, and I think it started working but I used the docker-compose up command without the 
-d
a
then just do it again...with 
-d
? 😛
j
I can't prisma deploy with either
It still says that localhost:4466 isn't running
wait I am uploading screenshots

https://snag.gy/QRYw2P.jpg▾

It works

https://snag.gy/mEuTzw.jpg▾

opened a new terminal to preserve the image running but running prisma deploy still emits the same error
n
can you share 
docker ps
?
j

https://snag.gy/P9oA3c.jpg▾

n
what is your 
prisma version
?
j
1.9 in image, 1.10 in cli
I'll update it first
after updating this happened:

https://snag.gy/glq0eX.jpg▾

It repeatedly said fatal errors that postgres hasn't started yet but after awhile it'll work but it didn't say it was successful in starting anything

https://snag.gy/Xw541b.jpg▾

Here is the current 
docker ps

https://snag.gy/7t0kja.jpg▾

it finally did after a while, but still couldn't prisma deploy
a
What happens when you do 
export DEBUG="*"
(and then prisma deploy)
j

https://snag.gy/1yu9Cb.jpg▾

I tried fixing the endpoint in 
prisma.yml
to postgres:5432 or 0.0.0.0:5432, none worked
a
🤷‍♂️ I am clueless
j
I've been clueless for more than 3 weeks now. 😞
😢 1
n
that's not the correct endpoint.
endpoint: localhost:4466/servicename/stagename
is the correct endpoint to be entered in 
prisma.yml
.
j
oh sorry it's really localhost:4466 earlier I just mixed it up my bad
sorry, servicename/stagename?
n
Please provide a bug report here, including a full repository + steps to reproduce this behaviour. It seems to be something subtle and Slack is not the best way to talk about this. Thanks. https://github.com/prismagraphql/prisma
👍 1
j
Okay will do. Thanks for replying @Arnab and @nilan. Appreciate your help
👌 2
Open in Slack
PreviousNext
Powered by