You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
------
> [build_image 6/8] RUN npx prisma generate:
#0 5.585 Prisma schema loaded from prisma/schema.prisma
#0 7.555 Error: Get Config: Unable to establish a connection to query-engine-node-api library.
#0 7.555 Details: Unable to require(`/app/node_modules/prisma/libquery_engine-linux-musl.so.node`)
#0 7.555 Error loading shared library libssl.so.1.1: No such file or directory (needed by /app/node_modules/prisma/libquery_engine-linux-musl.so.node)
#0 7.555
#0 7.555 Prisma CLI Version : 4.2.0
------
failed to solve: process "/bin/sh -c npx prisma generate" did not complete successfully: exit code: 1
@Mikle-Bond Interestingly enough, I don't have this issue on FROM node:16-alpine AS BUILD_IMAGE. However I do seem to have the following:
Error: Could not find Prisma Schema that is required for this command.
You can either provide it with `--schema` argument, set it as `prisma.schema` in your package.json or put it into the default location.
Checked following paths:
schema.prisma: file not found
prisma/schema.prisma: file not found
prisma/schema: directory not found
See also https://pris.ly/d/prisma-schema-location
I'm not sure which is causing this as 'migrate' says the following:
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "db.sqlite" at "file:/database/db.sqlite"
11 migrations found in prisma/migrations
No pending migrations to apply.
Seemingly without any apply history. (I'm trying to run it on a K3S cluster so it's definitely possible that, that's the issue.)
Describe the bug
The docker outputs this error:
I found this issue to be helpful: prisma/prisma#9624
I managed to build the image and spin up the project by changing
BUILD_IMAGE
tonode:14.17.1-alpine
, as suggested in one of the comments.I find this strange, as that issue was marked as resolved back in 2021.
Environment (please complete the following information):
docker version
listing below)The text was updated successfully, but these errors were encountered: