17 days ago
Hi,
I'm experiencing deployment failures with two services that were previously working correctly.
Both issues started around the same time.
1. Kong – Build Image Failure
My Kong service uses a custom Dockerfile (kong/Dockerfile).
The deployment:
- Completes initialization successfully.
- Fails at the Build Image stage after approximately 150 ms.
- Generates no actual build logs.
- Displays only a generic "Deployment failed" error.
Railway's Diagnose feature also couldn't identify the exact cause.
2. MinIO – Image Pull Failure
My MinIO service fails with the following error:
docker.io//minio/minio:latest couldn't be pulled from registry. Check that registry credentials for this service are still valid.
Both services were working before these failures started.
Troubleshooting so far:
- Checked the service configurations.
- Verified the Kong Dockerfile path.
- Used Railway's Diagnose feature.
- Checked deployment details.
I recently updated my Railway plan/usage limit, and these failures started around that time.
Could someone help investigate:
- Why Kong's image build fails almost immediately without generating build logs.
- Whether there are any registry or image-pull issues affecting MinIO.
- Whether this could be related to Railway's build infrastructure or recent platform changes.
Since multiple services are affected simultaneously, I'd appreciate help determining whether this is a platform-side issue or something specific to my project.
Thanks!
1 Reply
Status changed to Awaiting Railway Response Railway • 17 days ago
17 days ago
Kong and Console are failing because Railway can’t access the old source snapshot reused by those deployments. Start a fresh deployment using Deploy Latest Commit from the command palette, or push a new commit. Clicking Redeploy reuses the same snapshot and repeats the failure.
MinIO has a separate issue: Docker Hub is rejecting pulls of minio/minio:latest, which I also reproduced outside Railway. It needs an accessible replacement image; MinIO now provides instructions for building one from source. Before deploying a replacement, check its version against your existing MinIO data.
Neither error indicates that your plan or usage limit caused these failures.
Status changed to Awaiting User Response Railway • 17 days ago
3 days 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 • 3 days ago