a year ago
I am trying to deploy from an image hosted on Github Container Registry. Currently, not matter what I try, the deployment will keep running until I manually abort it. What's super weird, both the Deploy Logs and Build Logs are empty except for one time I saw this message:
=========================
Container failed to start
=========================
Failed to create deployment.
If this error persists, please reach out to the Railway team at https://help.railway.app.
I'm at a complete loss for how to proceed. Thanks in advance!
9 Replies
a year ago
Hi, it seems you're tagging with @latest. could you edit this to :latest ?
Best,
Nico
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
it's been a long Monday haha. Thanks for your help!
Status changed to Awaiting Railway Response Railway • over 1 year ago
a year ago
Looks like your latest issue is an expired token -
Requesting bearer token: invalid status code from registry 403 (Forbidden)Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
Hmm, weird, I just recreated the token. I'll take a look and make sure I'm using the right token again.
Status changed to Awaiting Railway Response Railway • over 1 year ago
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
Alright, could you see any other obvious issues? It's getting stuck again, but I just generated a new token to pull the image.
Status changed to Awaiting Railway Response Railway • over 1 year ago
a year ago
No more 403 error, from our current logs -
initializing source docker://ghcr.io/morel-tech/morel-api-dev:latest: reading manifest latest in ghcr.io/morel-tech/morel-api-dev: manifest unknownMeaning your image probably doesn't have a :latest tag, what tag does it have?
Also, sorry about the late reply here!
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
Thanks for your help! I thought Github Container Registry would automatically tag the last pushed image as 'latest', but I guess not.
Status changed to Awaiting Railway Response Railway • over 1 year ago
a year ago
That's more so dependent on what your build action tags it with.
I'm happy to see you have a successful deploy now, going to mark this as solved, but feel free to re-open if you have any more issues!
Status changed to Awaiting User Response Railway • over 1 year ago
Status changed to Solved brody • over 1 year ago