2 years ago
Our production app is not working, with errors saying:
"""
=========================
Container failed to start
=========================
activity StartToClose timeout
"""
This happens in the middle of the "Pushing" build script, and does not give us any other logs as a result. Please advise ASAP!
ⓘ Deployment information is only viewable by project members and Railway employees.
7 Replies
2 years ago
Hello @brody, thanks for the reply. Took me a bit on Chrome to figure out how to download, but here's the log.
Attachments
Status changed to Awaiting Railway Response Railway • over 1 year ago
2 years ago
You have a very large 6GB image, please work on writing a more efficient Dockerfile to get the image size as small as possible or you will likely continue to see this error.
2 years ago
Adding onto this - we have two other environments that are still labeled with "Deployment in Progress" despite them being deployed 21 hr ago:
2 years ago
@brody this is the Dockerfile that we are currently working with. The only exception out of the ordinary here is ffmpeg - can Railway not support it?
2 years ago
Had to repost, since the help site crashed:
@brody this is the Dockerfile that we are currently working with. The only exception out of the ordinary here is ffmpeg - can Railway not support it?
Attachments
2 years ago
Nothing at all to do with ffmpeg, This Dockerfile builds a 6GB image, please work on writing a more efficient Dockerfile that results in the smallest possible image.
Status changed to Awaiting User Response christian • over 1 year ago
7 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 • 7 months ago