-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"no binary found" using Docker example #1268
Comments
You are probably on an arm Mac, right? I can reproduce, I'll have to look closer into it |
Intel Mac, actually. Though I have teammates with ARM machines. I forgot to add a step after re-generating the client within the Dockerfile where I move the package to another location (the schema file comes from a git submodule) I added the generated Prisma files to my
I think I recall something about a For reference, the "generate" portion of my dockerfile now looks like: ENV PRISMA_GENERATOR_CLIENT go run github.com/steebchen/prisma-client-go
RUN go run github.com/steebchen/prisma-client-go generate
RUN cp ./prisma/db/* ./database/db
RUN rm -rf ./prisma/db |
Inspecting the filesystem within the
|
Interesting, as on my M1 mac it actually uses the arm64 binary and there's a different error. Thanks for the report though, I'll have to look closer into it when I have some time. For now as a temporary workaround please use a single-stage build then it will work fine |
Any updates on this issue? |
I'm trying to package my application into a Docker image following the guide here: https://goprisma.org/docs/reference/deploy/docker#optimized-dockerfile
The image builds fine, but when I run I get (pardon the JSON-formatted log output):
I did check for other issues and know this isn't the first issue about this error, but in my case:
Connect()
during anyinit()
functionsDockerfile looks like this:
.dockerignore is filtering out stuff like IDE files, the .git folder, locally-built app binaries on the dev's machine, etc., but I'm also running the generator again so that should be getting whatever binary I need for Linux, right?
The text was updated successfully, but these errors were encountered: