prisma: Query engine library for current platform "linux-musl" could not be found in Docker

Closing this as the issue has a clear solution here. Currently, Prisma Client might not work out of the box with some bundlers, if you encounter such a case, please create an issue, as we want to improve on this area.

I’ve removed my path aliases for now to work around that. It seems to be working now 🙏

I think it still might be a good thing to have troubleshooting somewhere in the docs with a few steps people can try? Small list I came up with from this issue and related issues:

• Clear cache
• binaryTargets
• Check bundling:
  • no bundling
  • bundling but copy static files to the right location (maybe add example on the module bundling page?)
• Refer to the alpine docker issues

I think that will save you guys a lot of new issues related to this topic 😅

For me you can close this issue!

FWIW, I ran into this problem running docker-compose locally with node:16-alpine. Thanks @barryhagan for pointing out the changes to latest Alpine. I decided to bump to 18 but pin to 3.16 as you suggested: node:18-alpine3.16 That worked for me.

I was able to resolve this after a bit of poking around. More info below.

Was getting this error after a docker run (it built fine):

Prisma Client could not locate the Query Engine for runtime "linux-musl-arm64-openssl-3.0.x".\n\nThis is likely caused by a bundler that has not copied "libquery_engine-linux-musl-arm64-openssl-3.0.x.so.node" next to the resulting bundle.\nEnsure that "libquery_engine-linux-musl-arm64-openssl-3.0.x.so.node" has been copied next to the bundle or in "dist".\n\nWe would appreciate if you could take the time to share some information with us.\nPlease help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation\n\nThe following locations have been searched:\n /home/node/app/dist\n /home/node/app\n /home/node/app/node_modules/@prisma/client\n /home/.prisma/client\n /tmp/prisma-engines

Some info on my local setup:

• Yarn version is 3.6.0
• Computer is Apple M1
• Bundler is https://github.com/vercel/ncc

Build command is:

yarn run ncc build src/index.ts -o dist

Dockerfile is:

FROM node:18.16-alpine3.17 AS builder

ARG NODE_ENV=production

ARG GH_NODE_AUTH_TOKEN

WORKDIR /home/node/app

# Git is used in later scripts
# Other packages needed for ARM chip if building image locally. For example, on Apple M1
# See https://github.com/parcel-bundler/watcher/issues/102#issuecomment-1229125545
RUN apk add --no-cache \
    git \
    make \
    clang \
    build-base \
    python3

# Enable yarn
RUN corepack enable

COPY . .

# Install packages
RUN yarn install --immutable --immutable-cache

# Run unit tests
RUN CI=true yarn test

# Do production build
RUN yarn run build

FROM node:18.16-alpine3.17 AS final

ENV NODE_ENV=production
ENV TZ=America/New_York

WORKDIR /home/node/app

# Tini is a container init system
# See https://github.com/krallin/tini
RUN apk add --no-cache tini

# Fix permissions
RUN chown node: /sbin
RUN chown node: /usr/local/bin

USER node

# Only copy needed files
COPY --from=builder --chown=node:node /home/node/app/dist /home/node/app/dist
COPY --from=builder --chown=node:node /home/node/app/generatedInfo.json /home/node/app/generatedInfo.json
COPY --from=builder --chown=node:node /home/node/app/schema.graphql /home/node/app/schema.graphql

EXPOSE 4001

ENTRYPOINT [ "/sbin/tini", "--" ]

CMD [ "node", "/home/node/app/dist/index.js" ]

To fix, had to specify the engineType to my prisma/schema.prisma:

generator client {
  provider   = "prisma-client-js"
  engineType = "binary"
}

See https://www.prisma.io/docs/concepts/components/prisma-engines/query-engine#configuring-the-query-engine

@gabo71096 if it helps, yarn version 4 has config options for os which you can tweak the pull the Windows and Linux binaries.

At schema.prisma file add:

generator client {
  provider = "prisma-client-js"
  binaryTargets = ["native","linux-musl"]
}

After that, run npx prisma generate

I had the same problem and struggled with it for a day. I want to share my experience with those looking for a solution if their setup is like mine. I’m using Turborepo, and I keep my Prisma in its related package as the Turborepo documentation suggests.

I tried to bundle my app using tsup, first I got an issue with finding the schema file, then after copying it to my build folder, I got the query engine platform error. by setting skipNodeModulesBundle: true in tsup config my problem has been solved.

@jkomyno no worries, anything to help 😄

I think it might simply be fixed by not using bundle: true in esbuild.ts. At least, I got the repro working by doing that (and removing the postBuild hook). Testing my application again at the moment.

I was just able to reproduce it also outside of Docker, however it might be related to my build step and there is no “actual” prisma issue related to the engine not being found, but rather a very confusing error message.

I’ve pushed my reproduction (built on @jkomyno’s proposed repro) to github: https://github.com/jclaessens97/prisma-repro

My guess is that when building with esbuild (I also have to add the postBuild step to place the schema in my build folder, otherwise it’s complaining it can’t find the schema), that some files are getting moved around (or not) and that it tries to reach some nescessary files using some sort of relative path.

However, I’m not sure which files, where I’m going wrong and how to fix it. On the other side if this IS the case (still not 100%), then I think Prisma can benefit from more clearer error messages 😄

EDIT: added expected repro output

TL;DR

I did some more research, and to me it seems that it’s looking for the ‘query engine library’ in the wrong location.

Context

I use a pnpm workspace with turbo. At first I noticed when opening a terminal in the docker, not everything was there. For example on my local machine I have @prisma in the root node_modules, but because of the prune (I think) it wasn’t there.

Next I tried building the docker without pruning, and the binary engine was there in the root node_modules for linux-musl-openssl3.x.so.node. However I found it in the @prisma/engines folder, while when believing the message it’s not looking there.

These are the places Prisma look:

/usr/src/app/.prisma/client
/usr/src/app/node_modules/.pnpm/@prisma+client@4.8.0_prisma@4.8.0/node_modules/@prisma/client
/usr/src/app/apps/api
/usr/src/app/apps/api/build
/usr/src/app/apps/api/build
/tmp/prisma-engines
/usr/src/app/apps/api/build

The location I’m referring to when I mean @prisma/engines, I mean this one: /usr/src/app/node_modules/.pnpm/@prisma+client@4.8.0_prisma@4.8.0/node_modules/@prisma/client

When I physically check in terminal inside the docker I can find the engine lib but it’s not at that location, it’s here: /usr/src/app/node_modules/.pnpm/@prisma+client@4.8.0_prisma@4.8.0/node_modules/@prisma/engines

But it’s not looking there.

When diving deeper into these engine locations, I found an environment variable that can be set for where to find each binary, including the missing libquery the error is about (as far as I can understand). Find the docs here.

I found the environment variable PRISMA_QUERY_ENGINE_LIBRARY that you can set to specify the ‘query engine library’ location. I understand correctly, this should normally only be used when you download or build these binaries yourself, not for the “auto downloaded” engines by Prisma.

Though I tried setting it to /usr/src/app/node_modules/.pnpm/@prisma+client@4.8.0_prisma@4.8.0/node_modules/@prisma/engines/libquery_engine-linux-musl-openssl-3.0.x.so.node to match the exact location of where I found the binary when looking into the docker with the terminal.

Now I’m stuck again. I’ve set the environment variable, double checked it’s effectively set, but still it doesn’t seem to look at that location. Maybe it does, but at least the issue remains the same, and the location of the environment variable isn’t added to the list Prisma prints out where it’s looking.

EDIT:

In the meantime I also tried adding a symbolic link that points the first location where Prisma looks /usr/src/app/apps/api/build/libquery_engine-linux-musl-openssl-3.0.x.so.node to the above location in the @prisma/engines folder.

Change node:18-alpine to node:18-alpine3.16 in your dockerfile for now.

Alpine 3.17 moved to OpenSSL 3.0 and that is now the tagged version for 18-alpine.

Alternatively, install the openssl1.1-compat package with 3.17.

Prisma on Alpine w/ OpenSSL 3.0 is not ready yet: https://github.com/prisma/prisma/issues/16553