NodeJS Nixpack - GLIBC_2.38 not found
pnpm install fails on some packages such as @sentry/cli and aws-crt while running their install scripts. It says /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.38' not found.
Here is a snippet from the logs
```
#10 11.74 Progress: resolved 1554, reused 0, downloaded 1553, added 1554, done
#10 12.22 .../[email protected]/node_modules/aws-crt install$ node ./scripts/install.js
#10 12.28 .../node_modules/@sentry/cli install$ node ./scripts/install.js
#10 12.34 .../[email protected]/node_modules/aws-crt install: node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.38' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)
#10 12.34 .../[email protected]/node_modules/aws-crt install: node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.36' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)
#10 12.34 .../[email protected]/node_modules/aws-crt install: Failed
#10 12.34 ELIFECYCLE Command failed with exit code 1.
#10 12.34 .../node_modules/@sentry/cli install: node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.38' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)
#10 12.34 .../node_modules/@sentry/cli install: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)
#10 12.34 .../node_modules/@sentry/cli install: Failed
#10 ERROR: process "/bin/bash -ol pipefail -c pnpm i --frozen-lockfile" did not complete successfully: exit code: 1
```Solution:Jump to solution
I think it would be best to move to a Dockerfile based build as you won't have any glib errors with a dockerfile
9 Replies
Project ID:
12e6dcd7-5c20-495b-bc51-c55e4971b90e12e6dcd7-5c20-495b-bc51-c55e4971b90e
Solution
I think it would be best to move to a Dockerfile based build as you won't have any glib errors with a dockerfile
that would be a good workaround indeed. but i have so many env vars i'll need to copy over to the dockerfile. i wanted to see if that could be avoided.
as i understand, docker can't just pick up the env vars from railway. i have to redeclare each and everyone.
not true, you would only need to define the variables in your dockerfile that you need during build
ah so if it's a nextjs application, like in my case, then i only need to declare the
NEXT_PUBLIC_ ones probably. thanks, i'll give that a shotsounds good!
awesome, it worked. i only needed to declare the
NEXT_PUBLIC_ ones indeed. thanksno problem!