a month ago
When deploying the most recent changes on my service, I am getting the following failure:
```
./blog_newsletter: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by ./blog_newsletter)
```
I have not changed anything related to the deployment of this service, so I am wondering if there is a recent change that has been made that is causing this versioning issue?
Thanks for your help!
3 Replies
a month ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
a month ago
The issue might be a GLIBC version mismatch between your build and runtime environments. Your binary was compiled with GLIBC 2.39, but Railway’s deployment environment has an older version that doesn’t include GLIBC_2.39.
I'd suggest moving to a Dockerfile base build as it is most reliable, since you won’t encounter GLIBC compatibility issues.
You can check this related issues and how they got fixed.
https://station.railway.com/questions/node-js-nixpack-glibc-2-38-not-found-de5eb4e4
https://github.com/railwayapp/nixpacks/issues/977
a month ago
As it happens, I am already using a Dockerfile build. But I found the issue -- it turns out it was a compatibility with the base Docker package I was using - https://github.com/LukeMathWalker/cargo-chef/issues/319.
Updating Debian in my Dockerfile fixed it.
Status changed to Solved sarahkb125 • 26 days ago