-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: version `GLIBC_2.38' not found (required by /nix/store/...) #3601
Comments
you will need to add packages to your nixpacks.toml if the default ones do not work or switch to using a dockerfile |
I switched to using dockerfile but did not have luck with that, I got another issue with this error: As for the To add more context to this issue, I used this with a Monorepo using Turborepo. Looking at this example: it says it's enough to just set the pack as nixpacks, yet after further exploring and @djsisson suggestion, I think there is a need to add extra nixpacks.toml file here like the laravel example. https://github.com/coollabsio/coolify-examples/tree/33a1f0e30758e5764ca012baefee7754e7f1843b/laravel |
Running into similar issues: I am using
|
@zaini the images used by nixpacks are not up to date (not much we can do), if you require a newer version of glibc you have to use a dockerfile |
Since we have no control over the Nixpacks repository, we cannot influence this, so the only option is to use a custom Dockerfile. See this issue to track when Nixpacks get updated railwayapp/nixpacks#1205. |
I am getting this error message whenever I try ot run next project on turborepo
Error Message and Logs
packages/ayasofyazilim-ui prepare: /app/packages/ayasofyazilim-ui/node_modules/.bin/../node/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /nix/store/c6r62m84hywf4i6qq1h28f13zv38yqyp-gcc-13.3.0-lib/lib/libstdc++.so.6)
Steps to Reproduce
related: #2550
Example Repository URL
No response
Coolify Version
v4.0.0-beta.341
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: