a month ago
Hi there--having trouble with deploys:
8+ consecutive deployment failures at container provisioning stage since May 13 20:52 UTC. Build succeeds and image is published but container never starts. Includes redeployments of previously successful commits with zero config changes. Deployment IDs: bcabff1a, bc901bd4, ee96f0fb and more
5 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Can anyone help here?
Status changed to Awaiting User Response Railway • 29 days ago
a month ago
Hi Ray--thanks for your help. I have re-deployed, again a failure, here is the diagnostic: This deployment failed at the container creation stage due to a persistent platform issue. The build and image publish completed successfully, but Railway could not provision a container. This has been happening across 13+ consecutive deployments since May 13, including redeployments of previously successful commits with no code or configuration changes.
Status changed to Awaiting Railway Response Railway • 29 days ago
a month ago
checking in here, still not resolved
23 days ago
Hey, sorry for the wait. We identified an issue where duplicate volume mounts were blocking container creation, and have been rolling out fixes for affected services. Can you try deploying again and let us know if it's still failing?
Status changed to Awaiting User Response Railway • 23 days ago
16 days 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 • 16 days ago