7 days ago
Hi,
I'm experiencing repeated container creation failures on a deployment that was working fine days ago. The build completes successfully every time, but the container fails to provision.
Details:
Deployment ID: acd33bdf-7179-4aaa-a91f-14ae45aff1a0
Service ID: 4f357e45-52ba-4000-a2cd-af06767c348e
Project: melodious-tenderness
Environment: production
What's happening:
Three consecutive deployment attempts on June 8 all fail at the CREATE_CONTAINER stage
Build succeeds every time; Docker image builds and pushes without errors
No deploy logs appear (container never gets provisioned)
The same commit (da23a0c) deployed successfully on June 6
The failing commit only modified files in desktop-app/ (CSS and version bump) — no changes to the service's root directory
This appears to be a platform-side infrastructure issue preventing container provisioning, not a code or configuration problem. I've already tried redeploying with no success.
Can you investigate why container creation is failing while the build pipeline works fine?
Thanks,
Kian
8 Replies
7 days ago
We're aware of these transient build queue issues and are actively working on improvements. If you continue to see failures, cancel any queued builds and wait before retrying, as additional redeploys can compound the issue.
Status changed to Awaiting User Response Railway • 7 days ago
Railway
We're aware of these transient build queue issues and are actively working on improvements. If you continue to see failures, cancel any queued builds and wait before retrying, as additional redeploys can compound the issue.
7 days ago
Would love some pointers please, as it's still unresolved...
Status changed to Awaiting Railway Response Railway • 7 days ago
7 days ago
Hi @railway -- sorry again, I really need some help. Users are impacted.
6 days ago
Hello?!!!!
6 days ago
This is an issue on our side, not your code or configuration. We identified a problem where container creation can fail after a successful build on services with a volume attached, and we're rolling out a fix for affected services. Failed deploys won't rerun automatically, so please trigger a fresh deploy and let us know here if it still fails at container creation.
Status changed to Awaiting User Response Railway • 6 days ago
3 days ago
Started failing for me today. When is the fix arriving?
Status changed to Awaiting Railway Response Railway • 3 days ago
noahd
This is an issue on our side, not your code or configuration. We identified a problem where container creation can fail after a successful build on services with a volume attached, and we're rolling out a fix for affected services. Failed deploys won't rerun automatically, so please trigger a fresh deploy and let us know here if it still fails at container creation.
3 days ago
Also started failing for us since today and user now can't enter our app because we can't fix bugs. Could you give us an update?
2 days ago
Hey all. Two different things happened in this thread, so untangling:
Kian: your June 8 issue was the volume-attach bug noahd mentioned, and that fix is deployed and holding.
For the folks who started failing June 12: that was new and unrelated, a networking issue on a subset of hosts (worst 13:00-15:00 UTC June 12) that broke container creation after successful builds. Resolved now.
Everyone: redeploy once and you should be through. Anything that still fails, post the deployment ID here and I'll trace it.
Status changed to Awaiting User Response Railway • 2 days ago