a month ago
I was having what appeared to be network issues, I then rebooted the container and it won't come up anymore. When I deploy I get this message from the chat helper:
This deployment failed during container creation due to a platform infrastructure issue. The build completed successfully and the image was pushed, but the platform was unable to schedule the container. This is the fourth consecutive failure of this type, with no errors in the build or configuration.
2 Replies
Status changed to Awaiting Railway Response Railway • 26 days ago
a month ago
I removed my attached volume and it booted
25 days ago
That was a platform-side scheduling issue on our end, not anything in your build or configuration. Your service was failing at the container creation step because of how the attached volume was being mounted, which is why detaching it let the deployment boot. Your service is up and running now.
If you need that volume reattached to the service, let us know and we can confirm it mounts cleanly so you get your persistent storage back without the failures returning. If you were running fine without it, no action is needed.
Status changed to Awaiting User Response Railway • 25 days ago
18 days 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 • 18 days ago