prisma: Prisma unable to load glibc with 3.0.1
Bug description
After updating Prisma from 3.0.0 to 3.0.1, I started getting TypeScript errors about .prisma/client locally (not on CI), so I thought I’d manually run npx prisma generate but it throws an error:
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: Unable to require(`/home/linux/Documents/prisma-api/node_modules/prisma/libquery_engine-debian-openssl-1.1.x.so.node`)
/snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/x86_64-linux-gnu/libcrypto.so.1.1)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Locally I use Ubuntu. In the changelog I saw something about RHEL, so could be related?
How to reproduce
- Update Prisma from 2.30.3 to 3.0.0
- Run npx prisma generate
- See above error
Expected behavior
No error.
Prisma information
No problem related to my prisma schema or queries
Environment & setup
- OS: Ubuntu 20.04
- Database: PostgresQL
- Node.js version: 14.17.3
Prisma Version
v3.0.0
Other Information
Checking my libc version by running file /snap/core/current/lib/x86_64-linux-gnu/libc.so.6
in terminal
Result :
/snap/core/current/lib/x86_64-linux-gnu/libc.so.6: symbolic link to libc-2.23.so
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 24 (8 by maintainers)
Solved by
snap remove node
, then install node manually from NodeSource. I’m on Ubuntu 21.04.Solved
Solved by removing Snapd then reinstall nodejs latest without snap and it worked correctly
https://github.com/prisma/prisma/issues/9174#issuecomment-921558437
Thank you!! This method worked to resolved my issue!
I ran into a similar glibc error running Pop!_OS 22.04 LTS:
I’m bumping this thread with details of my error to help future users 😄.
Updating the node version to 20.x.x fixed my issue.
Switching back to the old engine “solves” it for us too.
Ok, I reopen the issue for a better solution
Removing snapd is not a solution - would have to remove lots of packages (1password, vscode, ffmpeg, gimp, mediaingo, remmina, subtitleedit, vlc… ) and reinstall from elsewhere.
Any other idea? This shouldn’t be closed.