Build succeeds but deployment fails with registry timeout - us-west2

Project ID: d8f33022-30ab-450d-8b8f-5fe6364f473a Environment: production Service: ia72 Failed Deployment ID: 969d4601-9f0c-4f44-82b9-72b33d42f7ae

Problem: Build completes successfully (31.07 seconds) but deployment fails at CREATE_CONTAINER stage with a timeout error when trying to pull the image from the Railway registry.

Error Message:

/orchestrator.RouterLegacyService/CreateDeployment DEADLINE_EXCEEDED: ctrd: failed to pull/unpack image: failed to resolve reference "production-us-west2.railway-registry.com/61614004-92ad-4c7e-bedd-3e0196c3e499:969d4601-9f0c-4f44-82b9-72b33d42f7ae": failed to do request: Head "https://production-us-west2.railway-registry.com/v2/61614004-92ad-4c7e-bedd-3e0196c3e499/manifests/969d4601-9f0c-4f44-82b9-72b33d42f7ae": dial tcp 162.220.232.123:443: i/o timeout

What I've tried:

Multiple deployment attempts over several hours

Changed region configuration (service has a volume, so can't use multi-region)

Removed multi-region config to let Railway auto-assign region

Service Details:

Repo: openkabbalah/ia72 (main branch)

Build: Dockerfile (Node.js 20-slim, Next.js + Prisma + SQLite)

Volume: /app/data (persistent storage)

Port: 8080

This appears to be an infrastructure issue with the registry, not a code problem. The build succeeds consistently but fails at the container creation stage.

Solved

4 Replies

Yes, it's about a specific service:

Service ID: 61614004-92ad-4c7e-bedd-3e0196c3e499 Service Name: ia72 Project ID: d8f33022-30ab-450d-8b8f-5fe6364f473a Environment: production

Service Details:

Repo: openkabbalah/ia72 (main branch)

Build: Dockerfile (Node.js 20-slim, Next.js + Prisma + SQLite)

Volume: /app/data (persistent storage)

Port: 8080

Latest Failed Deployment ID: 36c773fb-3040-4fde-932a-bd59a9a17e2a

The build completes successfully every time (2:24 minutes), but fails consistently at the "Create container" stage when trying to pull the image from the registry. We've tried:

Multiple deployment attempts over several hours

Simplified the Dockerfile (reduced from 14 to 5 RUN layers)

Removed multi-region config

The error always points to a timeout resolving the image in production-us-west2.railway-registry.com.


Any news, please? 🙏


I got that too (build), I just re-build it and it worked


Now it works, thanks a lot!


Status changed to Solved 0x5b62656e5d about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...