4 months ago
The build keeps taking a long time and failing at the image build. Seems to be an issue with Railway.
Attachments
6 Replies
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
I'm getting the same error. Do you have a docker deployment? Here's where my deployment gets stuck: load metadata for docker.io/library/python:3.11-slim 9m 46s - then it throws the same error.
muzunogullari
I'm getting the same error. Do you have a docker deployment? Here's where my deployment gets stuck: load metadata for [docker.io/library/python:3.11-slim](http://docker.io/library/python:3.11-slim) 9m 46s - then it throws the same error.
4 months ago
Exactly!
4 months ago
Same for me
4 months ago
We're aware of issues with the Metal builder node you're hitting. Cancelling the failed build and redeploying may route you to a different builder and resolve it. If that doesn't work, let us know.
Status changed to Awaiting User Response Railway • 4 months ago
sam-a
We're aware of issues with the Metal builder node you're hitting. Cancelling the failed build and redeploying may route you to a different builder and resolve it. If that doesn't work, let us know.
4 months ago
It does not work unfortunately
Attachments
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
Apologies for the trouble. We have an ongoing incident, "Builds and deployments are slow to progress," affecting build machines and deployments across all regions. This is why redeploying isn't resolving it. You can follow updates here: https://status.railway.com/incident/cmm2cvzx50dxkx4rz5dx8efxh
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 4 months ago