Skip to content
Deployment fails with Container failed to start
pasi-mahonen
OP

9 months ago

Any ideas how to fix?

2026-02-18T14:05:58.737848192Z [inf] image push

2026-02-18T14:06:15.167241977Z [inf]

2026-02-18T14:06:15.167282863Z [inf] =========================

2026-02-18T14:06:15.167291473Z [inf] Container failed to start

2026-02-18T14:06:15.167296198Z [inf] =========================

2026-02-18T14:06:15.167302433Z [inf]

2026-02-18T14:06:15.167309245Z [inf] /orchestrator.RouterLegacyService/CreateDeployment DEADLINE_EXCEEDED: ctrd: failed to fetch image: failed to resolve reference "production-dpiad.railway-registry.com/7367d5ab-2e95-4623-82c8-2803752e9058:5c803338-6e16-42b2-82cd-5bfb5a0de5ad": failed to do request: Head "https://production-dpiad.railway-registry.com/v2/7367d5ab-2e95-4623-82c8-2803752e9058/manifests/5c803338-6e16-42b2-82cd-5bfb5a0de5ad": dial tcp 152.233.30.98:443: i/o timeout

2026-02-18T14:06:15.167315023Z [inf]

Closed

4 Replies

zakii

9 months ago

I have same problem on production for 2 days now. My system is running but not functional for clients. Very disappointing.


9 months ago

Should be all good now, but please let me know if you are still seeing this.


brody

Should be all good now, but please let me know if you are still seeing this.

pasi-mahonen
OP

9 months ago

All good now. Thanks !


yashasprivate3-ai

23 days ago

nice


Status changed to Closed brody • 23 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...