a year ago
project id: 1b326884-0c17-43ed-9b52-f443662e8f50
The error seems to be a platform issue and not a service issue.
=========================
Container failed to start
=========================
crun: unknown version specified: OCI runtime errorNothing has actually changed on my end, for this service, since the last deploy. So it shouldn't fail. Don't know what the issue might be, nor how to resolve. (going to bed, so not going to respond for a bit [probably]).
1 Replies
a year ago
!t
a year ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response brody • 11 months ago
a year ago
I've filed a ticket with the team. For now, you can try:
1) Redeploying
2) If that doesn't work, go into Settings -> Runtime -> Change V2 to Legacy
I ended up pushing a new build and the error didn't show up. I suspect this to be a very one off type of bug. But I am glad I didn't have to move to legacy.
railway[bot]
10 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please open a new thread if you require further assistance. Thank you!
Status changed to Solved railway[bot] • 10 months ago