Prisma•6mo ago

PrismaClientInitializationError with docker

Hi, i have this problem:

PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x".

This happened because `binaryTargets` have been pinned, but the actual deployment also required "debian-openssl-3.0.x".
Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it:

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

The following locations have been searched:
  /usr/src/app/dist/src/generated/client
  /root/eventapp/EventManagement-email-service/src/generated/client
  /usr/src/app/dist/src/.prisma/client
  /tmp/prisma-engines
  /usr/src/app/dist/prisma
    at Qu (/usr/src/app/dist/src/generated/client/runtime/binary.js:116:805)
    at async /usr/src/app/dist/src/generated/client/runtime/binary.js:168:2648 {
  clientVersion: '6.2.1',
  errorCode: undefined
}

Node.js v24.0.1

PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x".

This happened because `binaryTargets` have been pinned, but the actual deployment also required "debian-openssl-3.0.x".
Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it:

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

The following locations have been searched:
  /usr/src/app/dist/src/generated/client
  /root/eventapp/EventManagement-email-service/src/generated/client
  /usr/src/app/dist/src/.prisma/client
  /tmp/prisma-engines
  /usr/src/app/dist/prisma
    at Qu (/usr/src/app/dist/src/generated/client/runtime/binary.js:116:805)
    at async /usr/src/app/dist/src/generated/client/runtime/binary.js:168:2648 {
  clientVersion: '6.2.1',
  errorCode: undefined
}

Node.js v24.0.1

11 Replies

Prisma AI Help•6mo ago

You chose to debug with a human. They'll tinker with your query soon. If you get curious meanwhile, hop into #ask-ai for a quick spin!

514sid•6mo ago

Can you share your schema.prisma file without the models?

RedRossOP•6mo ago

generator client { provider = "prisma-client-js" output = "../src/generated/client" previewFeatures = ["typedSql"] binaryTargets = ["linux-arm64-openssl-3.0.x"] engineType = "binary" } datasource db { provider = "postgresql" url = env("DATABASE_URL") }

514sid•6mo ago

You need to add debian-openssl-3.0.x to binaryTargets:

binaryTargets = ["linux-arm64-openssl-3.0.x", "debian-openssl-3.0.x"]

binaryTargets = ["linux-arm64-openssl-3.0.x", "debian-openssl-3.0.x"]

RedRossOP•6mo ago

I have another microservice where it works with the same generator and dockerfiles, and they are from the same droplet of digital ocean, why does this happen?

514sid•6mo ago

afaik there are no ARM droplets on DO, so maybe you're targeting native on another service?

RedRossOP•6mo ago

ah I didn’t know, this is my system information: 6.11.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 12 11:25:41 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux, maybe it can be useful

514sid•6mo ago

Anyway, have you updated binaryTargets and tried again?

RedRossOP•6mo ago

i try now I also used npx prisma generate after add debian-openssl-3.0.x there are, I’m doing a new deploy @514sid it worked

514sid•6mo ago

Thanks for the feedback!

RedRossOP•6mo ago

Thank you very much for your availability

Gaming

Programming

PrismaClientInitializationError with docker

Did you find this page helpful?