5

I am really not familiar with docker, but I'm using docker to run a web app, which uses prisma/nexus

When I try to compose up, I get this error:

 Error: Unknown binaryTarget linux-arm-openssl-undefined and no custom binaries were provided

Can someone tell me what this error means, and how can I solve it? I think it has to do with the fact that docker doesn't support the OS that I'm working on, but I'm not entirely sure.

cassenav
  • 73
  • 1
  • 4
  • Does this answer your question? [Docker image run in m1 processor](https://stackoverflow.com/questions/66456627/docker-image-run-in-m1-processor) – jordanvrtanoski Mar 08 '21 at 13:58

3 Answers3

7

From the official docs,

Prisma Client consists of three major components.

  • JavaScript client library
  • TypeScript type definitions
  • A query engine (in the form of binary file)

While the generated code is cross platform (this is javascript), the query engine is not.

When you run the prisma generate command, prisma seems to uses the query engine, but it needs to find the proper binary for the current platform otherwise it throws an error.

The problem is for some reason I cannot explain (because I am having the same problem) the platform within the docker is not recognized as a supported platform one.

My guess is either docker is providing the wrong platform or there is a bug in prisma at some point, the error message linux-arm-openssl-undefined with undefinedin it could possibly be a clue of the problem.

Solution: Right now: I plan running my images on an x86 computer the time for this issue to be fixed. The latest docker 3 RC2 (released 5 days ago) did not help neither.

Note that you can specify binaryTargets into the schema.prisma file.

generator client {
  provider = "prisma-client-js"
  binaryTargets = ["debian-openssl-1.1.x"]
}

But for some reason, and even if I am building my docker image on top of a debian, this does not work. Prisma seems to recognize I am on linux-arm but is unable to associate a binaryTarget to. Also… is this platform really accurate ? Is docker running an linux arm under the hood or an x86 debian under rosetta ? I've no idea.

[EDIT] node images are Multi-Arch, meaning

FROM node:15.12.0-buster-slim AS builder

Will pick the linux architecture for my host platform (linux/arm64/v8) It seems we can actually build for x86 on m1 using buildx experimental feature according to this post

Flavien Volken
  • 16,172
  • 11
  • 86
  • 115
4

Undefined means you don't have openssl installed in the container. You can get correct binary target name by installing openssl. Add this to Dockerfile:

FROM node:16-slim
RUN apt-get update
RUN apt-get install -y openssl

Answer from here https://github.com/prisma/prisma/issues/861#issuecomment-881992292

Aleksandr Khaustov
  • 186
  • 4
0

I had the same issue when using node:alpine. First I tried to install manually openssl with apk add openssl but there were still some other issues raising.

I managed to solve it by switching to node:lts and adding to my Dockerfile RUN apt-get -qy update && apt-get -qy install openssl

Maka
  • 9
  • 1
  • Thanks this solution worked for me even though I am running a Macbook Air M1. Changing `alpine` to `lts`and `apk` to `apt-get` fixed the issue. – Renaud Dec 15 '21 at 16:32
  • Glad to hear it ! I am on a Macbook M1 as well – Maka Dec 16 '21 at 17:18