a month ago
My
service has been crash-looping since 2026-05-20 with error failed to exec pid1: No such file or
▎ directory. The volume mounts successfully but the postgres process cannot start. I need help recovering data from
▎ volume vol_5lovbbwwwwovcaj0 or fixing the container image while preserving the data. This is production data.
Attachments
2 Replies
a month ago
Your volume data is intact. The "failed to exec pid1" error is caused by a stale container image, and a normal redeploy does not re-pull the image, which is why redeploying hasn't helped. To fix this, open the command palette (Cmd/Ctrl+K) and select "Redeploy source image" - this will pull a fresh image and resolve the crash loop while preserving all your data on the volume.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your volume data is intact. The "failed to exec pid1" error is caused by a stale container image, and a normal redeploy does not re-pull the image, which is why redeploying hasn't helped. To fix this, open the command palette (Cmd/Ctrl+K) and select "Redeploy source image" - this will pull a fresh image and resolve the crash loop while preserving all your data on the volume.
a month ago
thank you, you save me. But ctrl+k can not work in windows, i need to use mac to run cmd+k. but it's back now
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago