Prisma 'PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "linux-musl"' or 'debian-openssl-3.0.x' in Docker, Alpine or serverless - how to set binaryTargets?

Cause: prisma-client-js ships a native query engine binary that is specific to the operating system and OpenSSL version. By default, prisma generate fetches the engine only for the machine where it runs (binaryTargets defaults to native). If you generate on macOS, Windows or a different image than the one that runs the app (for example generating on your laptop and deploying to Alpine, or a Debian image with a different OpenSSL), the matching binary is absent and startup fails with this error, which names the runtime it needed. Fix (best first): 1. Add the target platforms to the generator block in schema.prisma, keeping native for local work. Use the value the error message names, for example: generator client { provider = "prisma-client-js" binaryTargets = ["native", "linux-musl-openssl-3.0.x"] } The documentation lists examples such as debian-openssl-3.0.x (Debian 12, Ubuntu 22.04), linux-musl-openssl-3.0.x (Alpine 3.17 and newer, x86_64) and linux-musl-arm64-openssl-3.0.x (Alpine on ARM64). The openssl part must match the OpenSSL version on the target image. 2. Run npx prisma generate again inside the build stage of your Dockerfile (after copying prisma/schema.prisma), so the engine matches the final image. Copy the generated client and node_modules/.prisma into the runtime stage if you use multi-stage builds. 3. On Alpine, make sure the OpenSSL libraries expected by the engine are installed in the final image (the openssl package) and that the base image tag is the one you generated for. 4. Prefer using the same base image family for build and run. Slim Debian images also need OpenSSL installed if the engine reports it cannot find libssl. 5. Newer Prisma versions can run without the Rust engine (engineType = "client" with a driver adapter, since v6.16.0), in which case binaryTargets is unnecessary; check your Prisma version before relying on this. Verify: rebuild the image without cache, start the container and run a trivial query; the initialization error should be gone. Sources: https://www.prisma.io/docs/orm/reference/prisma-schema-reference https://www.prisma.io/docs/v6/orm/prisma-schema/overview/generators https://www.prisma.io/docs/v6/orm/reference/error-reference