a year ago
We had a deployment issue start last week. First deployment to fail was started at 2025-09-11T06:00:06.888598143Z.
```
2025-09-11T06:00:06.888598143Z [inf] 2025-09-11T06:00:06.888634410Z [inf] ========================= 2025-09-11T06:00:06.888639960Z [inf] Container failed to start 2025-09-11T06:00:06.888643618Z [inf] ========================= 2025-09-11T06:00:06.888649325Z [inf] 2025-09-11T06:00:06.888655854Z [inf] This image does not have a "08e0140a-dbbf-4075-b59d-5293ebe37fdd" tag. 2025-09-11T06:00:06.888659095Z [inf]
```
It has failed for the same reason around 50 times now with no resolution. The same commit deployed successfully 6 hours earlier.
8 Replies
a year ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Failed to start deployment
- 🧵 Failed to start container
- 🧵 Deployment failed during deploy process
- 🧵 Container failed to start postgres
If you find the answer from one of these, please let us know by solving the thread!
a year ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
a year ago
I'm a bit confused. I see that your Service is configured to build from a Dockerfile, but there's no Dockerfile in the root of your repository?
How are you building your container?
Status changed to Awaiting User Response Railway • 11 months ago
a year ago
we have it set with RAILWAY_DOCKERFILE_PATH
I just switched the root dir manually to api which failed due to docker context i believe and once i reverted it everything started working again. Not sure what's going on here
Status changed to Awaiting Railway Response Railway • 11 months ago
a year ago
Apologies but this looks like an issue with the application level code. Due to volume, we can only answer platform level issues.
I've made this thread public so that the community might be able to help with you query.
Status changed to Awaiting User Response Railway • 11 months ago
a year ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open jake • 11 months ago
a year ago
I'm not sure how you came to that conclusion. Nothing changed on our end, the build just started to fail. We changed a configuration in the dashboard, then reverted it and the build succeeded. No code difference, yet the build succeeded.
a year ago
We recently fixed an issue with expired image cleanup a couple days ago - have you noticed the issue reoccurring?
a year ago
✅ The ticket "Rebuild Code if Missing" has been marked as completed.