[SOLVED] Prisma won't build consistently with the same Dockerfile specs
Hi, when bundling an app with Prisma, it works on a
node:20 and node:20-alpine locally.
When building with the same machines on Github Action ubuntu-latest runner they fail with the following error:
For context, I'm trying to have both Accelerate (for Vercel) and Standalone (Long-running) together.
And here is the PR (including failed builds): https://github.com/dreampipcom/hypnos/pull/41
Only difference is the Docker Info (obviously) and my network settings (firewalls included).
Why is that so? Is there anything else I need to do?GitHub
ar(feat) [DPTM-8] [DPCP-88] [DPCP-81] [DPCP-118] Dockerize and GCP ...
PLEASE REVIEW YOUR OWN PR BEFORE OPENING/UN-DRAFTING IT
[Ticket Title]
[ticket description]
Screenshots/Videocasts/Preview Links
Have you?
Reviewed your own PR?
Tested your own feature/fix meets...
Solution:Jump to solution
Solved: Missing NEXUS_STANDALONE environment variable in "base as build" Docker execution context.
Rationale: in my local machine, the environment variable was available at a higher reference point....
2 Replies
Mentioned in: https://github.com/prisma/prisma/issues/25077
GitHub
Prisma won't build consistently with the same Dockerfile specs · Is...
Bug description Hi, when bundling an app with Prisma, it works on a node:20 and node:20-alpine locally. When building with the same machines on Github Action ubuntu-latest runner they fail with the...
Solution
Solved: Missing NEXUS_STANDALONE environment variable in "base as build" Docker execution context.
Rationale: in my local machine, the environment variable was available at a higher reference point.