Error: Prisma Client could not locate the Query Engine for runtime "linux-musl-arm64-openssl-3.0.x".

[Sakub]

Question

Hi, I'm facing the PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "linux-musl-arm64-openssl-3.0.x". issue and I saw it was already fixed some time ago. Sadly I'm still facing the problem. I'm running prisma inside docker container and I use the Apple M2 processor. I got told by one of the prisma repo members to create a discussion, so here I am. Could someone please help me up with this issue? Is there something I'm doing wrong? Here's my Dockerfile:

FROM node:alpine

WORKDIR /app

COPY package.json /app/package.json

RUN apk add openssl3
RUN npm install

COPY . /app
RUN npx prisma generate

EXPOSE 3000
CMD ["npm", "run", "start"]

And my schema.prisma:

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["linux-musl-arm64-openssl-3.0.x"]
}

I'm using Docker Compose, here's the file if it could help with something:

version: '3.8'
services:
  app:
    build: .
    ports:
      - "3000:3000"
    volumes:
      - .:/app
      - /usr/src/app/node_modules
    working_dir: /app
    command: npm run start:dev

  test:
    build: .
    volumes:
      - .:/app
    working_dir: /app
    command: npm run test

After running my app with docker-compose up --build im getting the following error:

test-1  | PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "linux-musl-arm64-openssl-3.0.x".
test-1  | 
test-1  | This happened because Prisma Client was generated for "darwin-arm64", but the actual deployment required "linux-musl-arm64-openssl-3.0.x".
test-1  | Add "linux-musl-arm64-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it:
test-1  | 
test-1  | generator client {
test-1  |   provider      = "prisma-client-js"
test-1  |   binaryTargets = ["native", "linux-arm64-openssl-3.0.x", "linux-musl-arm64-openssl-3.0.x"]
test-1  | }
test-1  | 
test-1  | The following locations have been searched:
test-1  |   /app/node_modules/.prisma/client
test-1  |   /app/node_modules/@prisma/client
test-1  |   /Users/sakubdev/node/goal-tracker-api/node_modules/@prisma/client
test-1  |   /tmp/prisma-engines
test-1  |   /app/src/infrastructure/database/prisma
test-1  |     at dl (/app/node_modules/@prisma/client/runtime/library.js:67:805)
test-1  |     at Object.loadLibrary (/app/node_modules/@prisma/client/runtime/library.js:114:9816)
test-1  |     at zt.loadEngine (/app/node_modules/@prisma/client/runtime/library.js:116:448)
test-1  |     at zt.instantiateLibrary (/app/node_modules/@prisma/client/runtime/library.js:115:10322) {
test-1  |   clientVersion: '5.7.1',
test-1  |   errorCode: undefined
test-1  | }

Error shows that I should include "native", "linux-arm64-openssl-3.0.x", "linux-musl-arm64-openssl-3.0.x" to my binaryTargerts array but if I do so then the problem still occurs.

What is worth mentioning if I do npx prisma generate and then run my app on my machine everything works fine, the issue occurs only with docker.

I managed to somewhat get around this issue by using node-slim docker image and installing openssl in Dockerfile

RUN apt-get update -y && apt-get install -y openssl

But I would really want to use the node-alpine image because of the reduced size of an image.

Could someone help me with fixing this issue? Thanks in advance for future responses :) (I'm really sorry if I may sound impolite or stuff like that - I have no intention of being so. I'm just really tired because its been a week since I tried to get past this error)

How to reproduce (optional)

No response

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

• OS: MacOs

• Database: SQLite

• Prisma version: 5.7.1

[britny-no]

me too!!

[monqyClouds]

This has been my issue for a while now, however, I've seen a solution which might work for you, add
COPY prisma ./prisma/
above "RUN npm install" and you don't need "RUN prisma generate". Nothing has worked for me so far, but I've seen several cases where it worked

[ludralph]

Hi @Sakub, Did you get a chance to try the suggestion above? Do let us know if it resolves your issue or not.

[monqyClouds]

This has been my issue for a while now, however, I've seen a solution which might work for you, add
COPY prisma ./prisma/
above "RUN npm install" and you don't need "RUN prisma generate". Nothing has worked for me so far, but I've seen several cases where it worked

Finally it worked for me, my issue was that I was referring to the host port instead of the container port in my db connection string as I was using docker compose for all my services. The initial suggestion still stands however.

[mattgraphlan]

for the internet searchers, I had a related bug where my github action was not downloading the additional engine binaries unless I set the env var PRISMA_CLI_BINARY_TARGETS
#23009

[IRediTOTO]

I have same error, it run fine on local but When I build to Vercel run to error. It only happended in server action.

Invalid `prisma.view.findFirst()` invocation:


Prisma Client could not locate the Query Engine for runtime \"rhel-openssl-3.0.x\".

We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.

This is likely caused by a bundler that has not copied \"libquery_engine-rhel-openssl-3.0.x.so.node\" next to the resulting bundle.
Ensure that \"libquery_engine-rhel-openssl-3.0.x.so.node\" has been copied next to the bundle or in \"prisma/generated/custom1\".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

The following locations have been searched:
  /var/task/prisma/generated/custom1
  /var/task/.next/server/app/(post)/sach
  /vercel/path0/prisma/generated/custom1
  /var/task/.next/server/app/.prisma/client
  /tmp/prisma-engines

[ai-is-awesome]

I have the exact same problem. Everything seems to work locally or when I'm using Prisma in the route handlers. But, I get this error if I try to use server actions. Were you able to figure out anything?

[teovillanueva]

same issue here