a year ago
we have been having many errors on our deploy, we think its that Libvips is not installed on the environment when we are building the image.
Notes
Upgraded libvips gem to latests version
This was a inconsistent issue but now has become a consistent problem where all builds fail.
ⓘ Deployment information is only viewable by project members and Railway employees.
5 Replies
a year ago
Hello,
All the successful builds and all the failed builds have been done with the exact same version of Nixpacks, so these failed builds are caused by changes on our side.
Perhaps a Dockerfile would be more suited here, it would give you the most control over your build.
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
Brody - any chance an LD_ config change has occurred? I'm seeing something related to that on some different issues / blogs related to GLIBC issues with nix packs
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
I'm asking because the build(s) we began to see failures on had no configuration changes - only cosmetic and documentation updates.
a year ago
We found the solution. there was a npm package that we added that caused problems
a year ago
Awesome I'm glad you found the solution, but to answer the question, nothing with the LD_ config has changed since all your builds have been on the same Nixpacks version.
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved brody • about 1 year ago