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.