I see the tag in Docker for the recently-released ...
# orm-helpd
Darryl
05/01/2019, 1:08 AMI see the tag in Docker for the recently-released 1.32.0 but I’m having trouble running
docker-compose up -d Copy code
Pulling prisma (prismagraphql/prisma/1.32.0:)...
ERROR: pull access denied for prismagraphql/prisma/1.32.0, repository does not exist or may require 'docker login'r
Ross Coundon
05/01/2019, 8:12 AMI don’t see that tag here
https://hub.docker.com/r/prismagraphql/prisma/tags
d
Darryl
05/01/2019, 11:14 AMWeird. I see it.
Darryl
05/01/2019, 11:14 AMr
Ross Coundon
05/01/2019, 11:49 AMWeird indeed, or maybe just tired as can see it now
Just tried a docker pull on it and it worked fine
i.e.
docker pull prismagraphql/prisma:1.32.0
Does that work for you? Or does it fail there and in docker-compose?
d
Darryl
05/01/2019, 12:17 PMYeah, I’ve also tried manually pulling and I get the same error. I spoke to a guy from Prisma and he said it’s likely a Docker issue as they’ve had some trouble the past couple of days.
r
Ross Coundon
05/01/2019, 12:47 PMThat’s still a bit odd as it’s working ok for me. Have you tried running
docker login
first?
d
Darryl
05/01/2019, 12:49 PMI have, yeah. I logged out first as well using docker logout. I log in fine and the config.json seems right. I’ve tried loads of times but about 5 minutes ago I could pull the image using docker pull but when I immediately tried docker-compose I got the same error.
r
Ross Coundon
05/01/2019, 1:42 PMI wonder if there’s something going on with your network, some occasional dropped packets maybe.
Ross Coundon
05/01/2019, 1:43 PMI’ve just tried myself with docker-compose (as my Heroku PostGres - Prisma connection got stuffed and had to recreate) and it worked fine
d
Darryl
05/01/2019, 1:51 PMNot sure. I’ve tried on a couple of different connections – both on and off VPN – and the results are the same. I guess I’ll try tomorrow. Thanks for helping dig into this with me.
r
Ross Coundon
05/01/2019, 2:12 PMNo worries, I know how frustrating these things can be. I guess you’ve tried removing the old Docker containers and images? Can’t see why that’d be a problem though. Also worth checking in case there’s some unprintable characters in the docker-compose.yml
Ross Coundon
05/01/2019, 2:35 PM#clutchingatstraws
d
Darryl
05/01/2019, 2:46 PMHaha. Thanks, but I’ve checked for those things as well. I went through the docker-compose file and then copied/pasted one from the docs and it was right. I’ll report back tomorrow. 👍
👍 1
Darryl
05/01/2019, 2:53 PM🤦
Darryl
05/01/2019, 2:55 PMFigured it out. Just as I was about to call it a night and go to bed. Sorry for wasting your time, man. It’s been one of those days. I was using the version 1.32.0 in my docker-compose.yml (as I would if I wanted to just pull that image) but it just needed 1.32. Thanks so much for sticking around. 🙏
Darryl
05/01/2019, 2:55 PMThis is what you get for trying to work when you’re supposed to be on holiday. 😄
r
Ross Coundon
05/01/2019, 2:57 PMHa!
Ross Coundon
05/01/2019, 2:58 PMWell, you’ll certainly sleep better 😄
d
Darryl
05/01/2019, 3:01 PMYep! Frustrating how I could pull the image with
.0r
Ross Coundon
05/01/2019, 3:55 PMYou too bud
4 Views