a month ago
Hello Railway Support,
Our MinIO service in the Pulse project cannot start because Railway fails
before container creation while pulling a public Docker Hub image.
Project ID: 397376f9-1fdd-469c-8cb0-fa7d6594369d
Environment: development (d7981ebd-b873-4dfd-a652-cb9d1aa8754a)
Service: MinIO (2beacb5d-db17-41a6-86b9-5a52271ab49f)
Latest failed deployment: 33014392-9ba9-4628-85a9-c9c6f92b61af
Failure time: 2026-09-13T02:13:32Z
Failure stage: CREATE_CONTAINER
Error:
The image "docker.io/minio/minio:latest" could not be pulled from the
registry.
If the image is private, check that the registry credentials saved for
this service are still valid.
The image is public: minio/minio:latest. No private registry credentials
are required or configured for this service.
The service fails before the MinIO process starts:
- build logs are empty;
- deploy/runtime logs are empty;
- the start command, persistent /data volume, and required MinIO variable
names are configured.
Could you please investigate Railway’s Docker Hub pull path for this
deployment, including registry egress, rate limiting, cache/manifest
resolution, and the worker/region used for the pull?
The Railway dashboard indicated that the same image had deployed
successfully recently, with no intentional configuration change.
Thank you.
5 Replies
a month ago
The deployment failed at CREATE_CONTAINER with a transient image-pull error. Your other services in the same environment deployed successfully at the same time, so this was not a broad connectivity issue. Open the MinIO service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image" to force a fresh pull of minio/minio:latest.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
The deployment failed at CREATE_CONTAINER with a transient image-pull error. Your other services in the same environment deployed successfully at the same time, so this was not a broad connectivity issue. Open the MinIO service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image" to force a fresh pull of `minio/minio:latest`.
a month ago
it didn`t help
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The image seems removed from the Docker Hub (checked on the website)
That's probably why it is failed to pull the image
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Hey — this looks like an upstream image removal, not a Railway credential issue.
The CREATE_CONTAINER error (docker.io/minio/minio:latest could not be pulled) is Railway doing what the docs say: a public Docker Image source pulls that tag from Docker Hub (https://docs.railway.com/services). Public Hub images do not need Registry Credentials (https://docs.railway.com/builds/private-registries). Empty build/runtime logs fit a failed pull before the container exists.
Redeploy / “Redeploy source image” still asks Hub for minio/minio:latest. Right now hub.docker.com/r/minio/minio/tags is 404, and MinIO’s README says community edition is source-only — they no longer publish pre-built container images (https://github.com/minio/minio). :latest is a moving pointer, so a tag that used to work can vanish (https://docs.railway.com/deployments/image-auto-updates).
What to do:
- Stop using
minio/minio:lateston Docker Hub. - Point the service at an image that still exists (e.g.
ghcr.io/<you>/minio:<tag>or another maintained MinIO-compatible image). Hub, GHCR, Quay, GitLab, MCR are documented (https://docs.railway.com/services). - Pin a tag or digest, not floating
:latest. - Keep your
/datavolume and MinIO env vars; only the image source needs to change for this error. - Redeploy. If it still fails, check the new path in your dashboard; add Registry Credentials only if that image is private.
With the Hub repo gone, the worker cannot pull that name regardless of region/cache. If you paste the new image reference (no credentials), we can check the path format.
mayori
The image seems removed from the Docker Hub (checked on the website) That's probably why it is failed to pull the image
a month ago
I checked templates on Railway and found this template created by someone from the Team
This template is not using the docker image but its Dockerfile is fetching the latest version of the minio/minio repo