3 months ago
Hi!
We have our Docker builds on GHCR. Been through several rounds ensuring we have the correct auth, but Railway is still not able to pull in the builds to deploy.
Build logs read:
Dec 16, 2025 at 10:16 PM
=========================
Container failed to start
=========================
We were unable to connect to the registry for this image. If you are using a private image, please make sure your credentials are valid. If this error persists, please reach out to the Railway team.
Thought it might be an auth issue, but went several rounds refreshing credentials to no avail.
Any insights greatly appreciated!
6 Replies
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Thank you, Brody. I upgraded to pro, but still getting the same error.
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Thank you. I have generated new credentials, but still getting the same error. When I click through the link for the file, it does take me to the correct page.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
I see now. There’s a field to add credentials right underneath the docker link that was not there before. Is there a need to have any shared variables for this?
3 months ago
No, shared variables or variables of any kind do not come into play when authenticating your image pulls.
Status changed to Awaiting User Response Railway • 3 months ago
3 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 • 3 months ago