this might be the important bit? 203949.042 0ns ?[34m0ns ?[34mnodist:shim-node?[0m - Going to execute the following binary: F:\WIN10\Program Files\Nodist/v-x64/11.13.0/node.exe environment FetchError: request to http://localhost:4466/management failed, reason: connect ECONNREFUSED 127.0.0.1:4466

docker ps => 8d6c11508d8a prismagraphql/prisma:1.34 "/bin/sh -c /app/sta…" 21 minutes ago Up 21 minutes prisma_prisma_1 ... but PORTS is empty, should there be a port here?

ran Kitematic - shows prisma_prisma_1 container. Environment Variables: PRISMA_CONFIG: value = port: 4466# uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security ... I do not need this to get started, right?

thank you for the suggestion of running Kitematic. From Kitematic I restarted the container and from Ports discovered that the published IP:PORT = 192.168.99.100 where the Playground exists! Maybe I should have specified that I am on Windows10? Thanks again - I can get on with learning Prisma and even though I thought I could get away with no Docker experience maybe it would be wise to take a Docker tutorial!

ok I spoke a little too soon but I think I am almost there. Playground is empty with no schema tab, and prisma deploy still fails. But now the docker ps shows correct container on 192..... but prisma deploy still fails because it is looking for localhost:4466. I have modified docker-compose.yml to remove "network_mode: host" and add ports: - "192.168.99.10044664466". So I think the question is: how to get prisma deploy to look at 192... instead of localhost....

Fixed! In prisma.yml endpoint was still pointing to localhost so "endpoint: http://192.168.99.100:4466" now allows prisma deploy to run correctly and playground at 192 .... shows schema tab with schema