search

prisma / studio

🎙️ The easiest way to explore and manipulate your data in all of your Prisma projects.
https://www.prisma.io/studio
1.89k stars 47 forks source link

Prisma studio can't be loaded from docker container, stuck with "getting things ready" #1062

Open jove4015 opened 1 year ago

jove4015 commented 1 year ago

Bug description

I have an app running in docker that uses prisma. I mapped the port 5555 to localhost so I could access the studio. I run "npx prisma studio" and I can start prisma studio just fine and connect to it, but it just says "Getting things ready...". When I check the developer console, there is a pending XHR to "/api" which just never seems to finish. There are no other errors, just that one pending request. On the CLI there is no unusual output.

The app works fine otherwise and there is no problem connecting to the database from inside the container. I made sure there are no other instances of prisma studio running in other browser tabs.

How to reproduce

  1. Install prisma in a docker container and expose port 5555.
  2. Open a web browser to http://localhost:5555/
  3. Observe that nothing finishes loading.

Expected behavior

Expected the studio to finish loading.

Prisma information

Environment variables loaded from .env prisma : 4.7.0 @prisma/client : 4.7.0 Current platform : darwin-arm64 Query Engine (Node-API) : libquery-engine 39190b250ebc338586e25e6da45e5e783bc8a635 (at ../../node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node) Migration Engine : migration-engine-cli 39190b250ebc338586e25e6da45e5e783bc8a635 (at ../../node_modules/@prisma/engines/migration-engine-darwin-arm64) Introspection Engine : introspection-core 39190b250ebc338586e25e6da45e5e783bc8a635 (at ../../node_modules/@prisma/engines/introspection-engine-darwin-arm64) Format Binary : prisma-fmt 39190b250ebc338586e25e6da45e5e783bc8a635 (at ../../node_modules/@prisma/engines/prisma-fmt-darwin-arm64) Format Wasm : @prisma/prisma-fmt-wasm 4.7.0-74.39190b250ebc338586e25e6da45e5e783bc8a635 Default Engines Hash : 39190b250ebc338586e25e6da45e5e783bc8a635 Studio : 0.477.0 schema.txt

Environment & setup

Prisma logs

No response

soulchild commented 1 year ago

I have seen this behavior as well and in my case Prisma Studio was stuck in that phase because it tried to download the engine binary again. Eventually the request timed out, because my provider by default does not allow outbound IP traffic to arbitrary IP addresses. Running prisma studio locally (not in a Docker container on our platform) works fine, because there is no outbound traffic restriction in place.

Maybe you have a similar issue? I've raised a bug report as https://github.com/prisma/studio/issues/1138