I'm trying to build a Docker image with a NestJS + Prisma application. I just switched from Windows to Mac Monterey OS (on M1 Pro) yesterday. I could build the image on my Windows machine, but now I can't build it on my Mac. Here's the error I'm receiving.

Error: Unknown binaryTarget linux-arm64-openssl-undefined and no custom engine files were provided

When I searched that on Google, the first hit was specifically about Prisma: https://github.com/prisma/prisma/issues/861 And that one led me to a pretty detailed conversation https://github.com/prisma/prisma/issues/5245 The conversation says near the end, in July 2021:

"This will be available for eveyrone with 2.27.0".

I'm on v

3.15.1

My base image is

node:16.15.1-alpine

. Anyone have any advice or point me toward further discussion? Alternatively, would it be worth trying to update the binary targets in the Prisma config manually? Actually - should I specify the binary target for the eventual target - which will be a Cloud Run instance? My generator client:

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

What have you specified in your binaryTargets in your schema.prisma?

Thanks for the reply.

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

yeah its like prisma can't detect what openssl version you have hence the undefined. might need to open an issue

I think it's actually my local machine that's having the problem - somehow. I was able to create images on my Windows machine (which now has an unrecoverable BIOS). I can run

npx prisma generate

and run a local server. I don't think this has anything to do with Cloud Run yet - I'm just trying to locally build a container right now.

we have a few different types of dev envs, and deploy to alpine docker container. our targets look like

binaryTargets   = ["native", "linux-musl", "debian-openssl-1.1.x", "darwin-arm64", "darwin"]

I had same problem, fix it by change

node:16-alpine

to

node:lts

and

RUN apk update && apk add dumb-init

to

RUN apt-get -qy update && apt-get -qy install openssl && apt-get -qy install dumb-init

in docker file