a month ago
Hello Railway Support,
I'm trying to deploy a MySQL service using the Docker image mysql:9.7.2, but the deployment consistently fails during the "Deploy → Create container" step.
The error shown in the deployment logs is:
"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."
The image I'm trying to deploy is:
mysql:9.7.2
The deployment reaches the Initialization step successfully, but fails immediately when trying to create the container. The service is therefore offline.
I am using the official MySQL Docker image and it should be a public image, so I don't believe authentication credentials should be required.
Could you please check whether there is an issue with Railway's connection to the Docker registry / Docker Hub for this deployment or region?
Region: US West
Deployment: Docker
Image: mysql:9.7.2
I've attached a screenshot of the deployment error.
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
That error means the registry refused the pull as a credentials or package-visibility problem. Using the exact token saved in Railway for this registry, run docker buildx imagetools inspect docker.io/library/mysql:9.7.2
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 • about 1 month ago