Running into "We were unable to connect to the registry for this image"

6 months ago

Hey team, I keep running into 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.

Trying to deploy using a docker image from a private image registry (ghcr.io). Everywhere I look it says I should be able to enter credentials under Settings > Source for the service in Railway but its just not there for me. Ive seen screenshots where its promting right under Source Image but mine just looks like this. Are private packages not supported on hobby plans?

pid: d5e38717-1226-470d-9f38-63dac96c94da

Solved

7 Replies

6 months ago

Private registries are only available on Pro. I'm curious to know where you read that you can enter credentials without mentioning that it's Pro only.



6 months ago

<:sadcat:786868978382536704>


6 months ago

I must be blind; I don't see where it mentions image credentials.


6 months ago

the credentials section ive seen mentioned by others whove run into this in my search for help but ive kind of just been piecing information together. but clearly im blind because i just reread this and its in there. not the most obvious but its there https://docs.railway.com/guides/services#deploying-a-private-docker-image


6 months ago

better?

1419801395632279800


6 months ago

!s


Status changed to Solved brody 6 months ago


Loading...