<@U6A7WT4SV> let's use this thread to discuss
# prisma-whats-new
n
@peter let's use this thread to discuss
p
hey nilan, any ideas?
h
@peter looks like you'll have to delete the existing containers
n
sure, what's your previous version?
also, do you mind your local data being wiped, or not?
p
previous docker for mac? or prisma image?
would prefer not to wide local data
n
aha, misread what you wrote earlier
I thought you upgraded the prisma cluster, not docker
h
does exporting work?
n
in your screenshot, the first line says "booting..." what did you do to end up there?
p
export what?
I had my local cluster running well for the past week….20 min ago I see notification from Docker for Mac that a new build of docker is avail…i install it and when I go to start working again, the prisma and mysql containers throw the error that it cannot create container for these two services
n
Which command did you run in the shell that resulted in this output?
p
yarn prisma local start
n
try
yarn prisma local stop
,
yarn prisma local start
p
ok ran both commands,
stop
produced “Booting local cluster 5.8s”
start
gave me the same error from the photo i posted
n
I'm out of ideas for now, please provide a full bug report here, so I can take a look later: https://github.com/graphcool/prisma 🙂
p
ok thanks nilan, i have a feeling this is more related to docker…have a good night!
n
It is! but the Prisma CLI should be resilient against upgrading Docker for Mac. If you want to dig deeper, I think you can look into docker volumes, we use them:
docker volume ls
👍 1
p
@nilan where can I find the configuration for the prisma service? i want to check my config against the defaults from prisma
n
what do you mean when saying prisma service?
p
prisma docker image
n
Gotcha! Prisma Service typically refers to a single service with a datamodel and a Prisma API.
p
thank you
n
here's the
docker-compose.yml
file, you need to cross compare with your
prisma
version, you should be able to find it in your global
node_modules
as well
oh, you ran
yarn prisma
, so it's likely a local
node_modules
.
p
solved the problem, although I don’t know why this occured. Had to manually set the
prisma
container to expose port 4466
n
Interesting! I'd still appreciate a bug report so we can ensure that this doesn't occur in the future.
Your solution also might help others running into this 🙂
n
thanks, that's super helpful! how did you actually update the container to expose the port?
p
no problem. I added some details to the bug report about possible fix 🙂
n
awesome, now it's almost a tutorial 😄 🙏