2 months ago
railway deploy of a docker image fails after 26 minutes creating containers
There are no deploy logs and diagnosing the failure says that the diagnosing failed.
7 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 months ago
2 months ago
architecture mismatch and health-check binding are the two most common self-inflicted causes — worth ruling those out first before assuming it's Railway's infrastructure..
Download the full logs via Ctrl+K → "Download Logs" on the deployment page
Try railway up from the CLI directly instead of the dashboard
Post in the Railway Help Station (station.railway.com) with your service ID — Railway staff actively triage these and often it's a known infra-side scheduler bug rather than anything on your end.
2 months ago
An image I built myself and that runs locally fine (using docker desktop). The image is linux/amd64 and so should be fine.
https://hub.docker.com/repository/docker/giltayar/monnaie-app/general
2 months ago
I can't access it, is it a private image?
If it's a private image, You need to upgrade to Pro Plan to be able to use private credentials
Or just deploy the repo and Railway will automatically build the image using Dockerfile in your repo
2 months ago
Sorry, I gave you my private link and not the public one: https://hub.docker.com/r/giltayar/monnaie-app
2 months ago
And this is the version I'm trying to deploy https://hub.docker.com/layers/giltayar/monnaie-app/0.6.2/images/sha256-841e593153294cdadfc73407ea64cdeeebff626c2cd893b6de8240207cdc4b32
2 months ago
NVM, I found the problem - I used @ instead of : to separate the image name from the version 🤦♂️
Status changed to Solved mayori • 2 months ago