25 days ago
I host a rails app on Railway and it's been hosted there since 2023. It uses Nixpacks. The deployment started failing yesterday in the build phase. rbenv install step seems to be failing. The problem is not in the code. The same code got deployed on Staging and Sidekiq successfully.
The agent has been misdiagnosing the problem too. I have never used GEM_HOME environment variable and I don't know where to change this. I can't even switch to Railpacks as agent keeps suggesting. Check the staging environment where I have switched to Railpacks, the deployment keeps crashing.
I have been stuck in this loop for the past 24 hours and I need to urgently release some code fixes.
Pinned Solution
25 days ago
Hello saurabhbhatia;
the root cause is that nixpacks is officially deprecated and in maintenance mode. it no longer gets fixes so the rbenv install step can break at any time with zero changes on your end
the safest fix right now is to switch to a dockerfile instead of fighting either nixpacks or railpack. a dockerfile bypasses both builders completely and gives you full control over the ruby version and build steps railway supports dockerfiles natively, no extra config needed
for the railpack issue on staging, you need to manually set your start command in the service settings instead of letting railpack auto-detect it, that is most likely why it keeps crashing
Hope this help you :)
2 Replies
25 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 25 days ago
25 days ago
Hello saurabhbhatia;
the root cause is that nixpacks is officially deprecated and in maintenance mode. it no longer gets fixes so the rbenv install step can break at any time with zero changes on your end
the safest fix right now is to switch to a dockerfile instead of fighting either nixpacks or railpack. a dockerfile bypasses both builders completely and gives you full control over the ruby version and build steps railway supports dockerfiles natively, no extra config needed
for the railpack issue on staging, you need to manually set your start command in the service settings instead of letting railpack auto-detect it, that is most likely why it keeps crashing
Hope this help you :)
24 days ago
Thanks @domehane thank you so much for your reply. I ended up writing a Dockerfile for the project. Just a little disappointed with the platform as I considered Railpack to work out of the box. appreciate the help.
Status changed to Open ray-chen • 24 days ago
Status changed to Solved ray-chen • 24 days ago