Unable to establish a connection to query-engine-node-api library using node:16-alpine3.17 #16762
Labels
bug/1-unconfirmed
Bug should have enough information for reproduction, but confirmation has not happened yet.
kind/bug
A reported bug.
team/client
Issue for team Client.
tech/engines
Issue for tech Engines.
topic: openssl
Bug description
When using docker image node:16-alpine3.17
npx prisma generate
encounters the following error in my bitbucket pipeline...when viewing the build information that bitbucket pipeline provides I see this docker image information.
I've been able to get around the current issue by specifying
node:16-alpine3.16
as that was my last working version.My current hypothesis is that there is an issue using openssl 3.0 because alpine3.17 makes it the default...
I believe I'm seeing this now because I previously had
node:16-alpine
as my defined docker image in my bitbucket-pipeline.yml, and the tag was changed today to point toalpine3.17
I'm not familiar with the prisma codebase but I did see that there is a parser function that the tests indicate some sort of matching. Perhaps that's not operating correctly in this case?
Also note that I use
linux-musl
in my prisma.schema generator and maybe that's also part of the problem as well?Thanks for your input!
How to reproduce
For the problem
node:16-alpine
ornode:16-alpine3.17
npx prisma generate
in the imageFor a work around
node:16-alpine3.16
npx prisma generate
in the imageExpected behavior
When using
node:16-alpine3.17
docker image and runningnpx prisma generate
in the image I expect to see a successful client generation like the following...Prisma information
Environment & setup
Prisma Version
My local version, but the problem is seen in a docker image
The text was updated successfully, but these errors were encountered: