a month ago
Good Morning/Afternoon/Evening sir/madam,
Whilst trying to deploy my docker image, each time I get an 404 of not found for the docker public image.
Images used are public for example, https://hub.docker.com/r/ferracorp/jaykia-server, yet when I place in the image during deployment, ferracorp/jaykia-server:latest, I find railway always appends docker.io hence docker.io/ferracorp/jaykia-server:latest, which this one here doesn't exist even when searching it online but the image does exist, but funny enough, not sure how, but after sometime it did deploy not sure how though, but currently its behind in updates since I've made and pushed changes to GitHub whilst building and pushing to docker. I've also provided my registry details on the env variables but no change whatsoever.
How exactly can I fix this, is there something I'm missing or an actual issue on railway?
Regards,
Fellow railway user.
3 Replies
a month ago
Prepending docker.io/ to Docker Hub image references is standard Docker behavior, not a Railway-specific issue. docker.io/ferracorp/jaykia-server:latest and ferracorp/jaykia-server:latest resolve to the same image. If the image is public on Docker Hub, it should pull without issues. To pick up new pushes to your image automatically, you can enable Image Auto Updates in your service's Settings under the Source section, or manually trigger a redeploy from the dashboard or CLI (railway redeploy) after pushing a new image.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Prepending `docker.io/` to Docker Hub image references is standard Docker behavior, not a Railway-specific issue. `docker.io/ferracorp/jaykia-server:latest` and `ferracorp/jaykia-server:latest` resolve to the same image. If the image is public on Docker Hub, it should pull without issues. To pick up new pushes to your image automatically, you can enable [Image Auto Updates](https://docs.railway.com/deployments/image-auto-updates) in your service's Settings under the Source section, or manually trigger a redeploy from the dashboard or CLI (`railway redeploy`) after pushing a new image.
a month ago
Ok, however still resolves to a 404 of image not found
Attachments
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The failed deployment shows that Docker Hub is returning "image not found" for that image reference, meaning the image or tag is not currently publicly accessible on Docker Hub. You mentioned setting registry credentials via environment variables, but that won't work. Registry credentials must be configured in your service's Settings under Source > Registry Credentials, and that feature requires the Pro plan - it is not available on Hobby.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 27 days ago