Container failed to start - activity StartToClose timeout
Everything was working fine before, but when I pushed a few more files (about 1gb) in my latest commit, I am getting this error. Does anyone know if there is a limit of container size in railway? Is it related to the chosen plan?
8 Replies
Project ID:
973cd3bd-df65-46d3-8077-b88fdd28703f973cd3bd-df65-46d3-8077-b88fdd28703f
Hey @mahrez,
Appologizes about that. You caught the start of an #🚨｜incidents in which builds were failing to go out. We quickly disabled builds and resolved the issue. If you redeploy it should go out just fine.
Perfecttt ill do thar right now
Hmm okay I see the issue now. The final image size is >5GB which is causing timeouts when we try and pull it. Surprisingly this hasn't really been an issue before. I will monitor this deploy and put a fix in place later today if it doesn't go through.
If possible though, I recommend decreasing the final image size as that will really speed up your deploys. Not sure if there are any large artifacts within the codebase that is causing the size to grow like this
The thing is the image is large because it contains high quality pictures that are all require for a task, would increasing the plan fix the issue?
Can you try deploying again
I'll try right now