2 months ago
Deployments failing with "Container failed to start" after successful builds.
Service: faicy.up.railway.app
Region: us-east4-eqdc4a
Issue: Build completes successfully (~40s), image pushes fine (98.6 MB), but then Railway waits 27 minutes and fails with "Container failed to start" → "Failed to create deployment".
Started 2+ hours ago. Previous deployment works fine (currently rolled back).
Build logs show successful completion but deployment fails on container creation step.
Already posted in Discord #help but no response yet. This appears to be an infrastructure issue on Railway's side.
14 Replies
2 months ago
Hey, is this still happening? Please provide the service id if this is the case, I'll raise this to the team afterwards.
2 months ago
nvm it's working now
2 months ago
also facing this issue
2 months ago
Tried it multiple times still same
2 months ago
Still facing the issue. I’ve added two follow-ups in the this thread, but have not received a response and this is now blocking my deployment.
Can anyone confirm from your side why the container is failing to start (crash reason, healthcheck failure, OOM, port binding, etc.)?
If this requires internal logs/inspection, please escalate to the appropriate team.
If there’s a known incident affecting deploys, please point me to it.
2 months ago
Hello everyone on this thread, can you provide links to the service such that we can go in and investigate each workload?
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
sup-rith
We have the same issue on our service too: https://railway.com/project/b914b1cb-c7e0-4b0c-9ea6-c73996eabc07/service/af8229e3-a97b-4f8a-b7ec-55623806c400/settings?environmentId=8124dfc5-1932-462e-a9f5-86840aaee393#deploy-region-config
2 months ago
This is all we have in the logs. Build is successful
Attachments
2 months ago
Hello!
We've escalated your issue to our engineering team.
We aim to provide an update within 1 business day.
Please reply to this thread if you have any questions!
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Any progress on this still facing same issue
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Hey Ankit!
For your project specifically, I see it deployed successfully 6 hours ago, were you still having issues elsewhere?
Status changed to Awaiting User Response Railway • 2 months ago
2 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 • 2 months ago
2 months ago
✅ The ticket Workload scheduling issue has been marked as completed.