segmentation faul during prisma generate with ubi9 base docker image #28088

tlukac60 · 2025-09-11T17:51:47Z

tlukac60
Sep 11, 2025

Question

We are encountering a segmentation fault in prisma generate step during docker image build when using a ubi9 based nodejs base image. The same exact docker build works fine without segmentation fault when the base image is an alpine based nodejs image (node:22.16.0-alpine3.21). The output of the docker build is shown below:

  [5/7] RUN cd /code/config-service   && npx --verbose prisma generate --no-hints
    → npm verbose cli /usr/bin/node-22 /usr/lib/node_modules/npm/bin/npm-cli.js
    → npm info using [email protected]
    → npm info using [email protected]
    → npm verbose title npm exec prisma generate --no-hints
    → npm verbose argv "exec" "--loglevel" "verbose" "--" "prisma" "generate" "--no-hints"
    → npm verbose logfile logs-max:10 dir:/root/.npm/_logs/2025-09-11T17_32_16_259Z-
    → npm verbose logfile /root/.npm/_logs/2025-09-11T17_32_16_259Z-debug-0.log
    → npm verbose stack Error: command failed
    → npm verbose stack     at promiseSpawn (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:22:22)
    → npm verbose stack     at spawnWithShell (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:124:10)
    → npm verbose stack     at promiseSpawn (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:12:12)
    → npm verbose stack     at runScriptPkg (/usr/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script-pkg.js:77:13)
    → npm verbose stack     at runScript (/usr/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script.js:9:12)
    → npm verbose stack     at run (/usr/lib/node_modules/npm/node_modules/libnpmexec/lib/run-script.js:48:10)
    → npm verbose stack     at async exec (/usr/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:154:16)
    → npm verbose stack     at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9)
    → npm verbose stack     at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5)
    → npm verbose pkgid [email protected]
    → npm error path /code/config-service
    → npm error command failed
    → npm error signal SIGSEGV
    → npm error command sh -c prisma generate --no-hints
    → npm verbose cwd /code/config-service
    → npm verbose os Linux 6.6.87.2-microsoft-standard-WSL2
    → npm verbose node v22.16.0
    → npm verbose npm  v10.9.2
    → npm verbose exit 1
    → npm verbose code 1
    → npm error A complete log of this run can be found in: /root/.npm/_logs/2025-09-11T17_32_16_259Z-debug-0.log

We are trying to understand the cause of this (are there any known issues with prisma & ubi9 w/openssl 3.2.2) and possible steps we can take to diagnose it further and/or resolve.

How to reproduce (optional)

Run docker build on ubi9 base image that invokes a prisma generate. I think schema doesn't matter here as we are not changing anything between alpine and ubi9 base images.

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

// Add your schema.prisma

// Add any relevant Prisma Client queries here

OS:
Database:
Node.js version:
Run prisma -v to see your Prisma version and paste it

nurul3101 · 2025-09-12T14:42:06Z

nurul3101
Sep 12, 2025
Maintainer

Hi @tlukac60!

Is this happening in latest prisma version 6.16.1?

Also what happens if you set engineType = "binary" in your schema.prisma file? Do you still get the same error?

5 replies

tlukac60 Sep 12, 2025
Author

Hi @tlukac60!

Is this happening in latest prisma version 6.16.1?
Currently our project is based on prisma verion 6.15.0. I'm not really sure what it would take to move to 6.16.1 but if you think that newer version would resolve this issue we can give it a try.

Also what happens if you set engineType = "binary" in your schema.prisma file? Do you still get the same error?
Yes, I have tried that but still get the same error.

AI suggests that the issue has to do with openssl version incompatibility, but not clear how that can be overcome?

I can upload core generated by node process during 'npx prisma generate' step if that would help you diagnose it better.

tlukac60 Sep 12, 2025
Author

Just tried with 6.16.1 and same result.

nurul3101 Sep 15, 2025
Maintainer

Do you mind trying out the Rust Free ORM version, which is going to be the default in Prisma 7 and check if you get the same error?
https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/no-rust-engine

This would help in identifying if this was related to prisma engines issue.

tlukac60 Sep 16, 2025
Author

Do you mind trying out the Rust Free ORM version, which is going to be the default in Prisma 7 and check if you get the same error? https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/no-rust-engine

This would help in identifying if this was related to prisma engines issue.

Tried the no-rust engine and believe I got it working OK with one service on alpine but then when I switched to ubi9 I got the same exact segmentation fault.

nurul3101 Sep 17, 2025
Maintainer

Hmm, so this something related to ubi9 image.
Could you open a GitHub Issue so that ORM team can have a look?

https://github.com/prisma/prisma/issues

2025-09-25T00:32:31Z

github-actions[bot]
bot Sep 25, 2025

Hi,

As we have not heard back from you, we are closing this discussion to keep our discussions organized.

Feel free to start a new discussion if this remains relevant.

Thank you for being part of the community!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

segmentation faul during prisma generate with ubi9 base docker image #28088

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 5 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

segmentation faul during prisma generate with ubi9 base docker image #28088

Uh oh!

tlukac60 Sep 11, 2025

Question

How to reproduce (optional)

Expected behavior (optional)

Information about Prisma Schema, Client Queries and Environment (optional)

Replies: 2 comments · 5 replies

Uh oh!

nurul3101 Sep 12, 2025 Maintainer

Uh oh!

tlukac60 Sep 12, 2025 Author

Uh oh!

tlukac60 Sep 12, 2025 Author

Uh oh!

nurul3101 Sep 15, 2025 Maintainer

Uh oh!

tlukac60 Sep 16, 2025 Author

Uh oh!

nurul3101 Sep 17, 2025 Maintainer

Uh oh!

github-actions[bot] bot Sep 25, 2025

tlukac60
Sep 11, 2025

Replies: 2 comments 5 replies

nurul3101
Sep 12, 2025
Maintainer

tlukac60 Sep 12, 2025
Author

tlukac60 Sep 12, 2025
Author

nurul3101 Sep 15, 2025
Maintainer

tlukac60 Sep 16, 2025
Author

nurul3101 Sep 17, 2025
Maintainer

github-actions[bot]
bot Sep 25, 2025