Container failed to start // Failed to create deployment
firstmark-dev
PROOP

17 days ago

Deploy is failing after stalling for 20 minutes,

start command:
uvicorn main:app --host 0.0.0.0 --port ${PORT:-8080}

Using railway metal for build.

only error logs are in build
image push

756.8 MB / 756.8 MB21.1s

=========================

Container failed to start

=========================

Failed to create deployment.

Nothing in deployment logs

Awaiting User Response

35 Replies

Hey there,

First off, sorry for the poor experience. We did trace it to a situation to a host that the low forwarding was impacted. This is now resolved, if you can trigger another build, we can go ahead and debug that with you.


Status changed to Awaiting User Response Railway 16 days ago


fantaztig
PRO

16 days ago

Seeing a similar issue, deploy fails, now deployment logs only build logs indicating failed health checks


Status changed to Awaiting Railway Response Railway 16 days ago


victor-floriano
HOBBY

16 days ago

I was having this same issue, removed metal for build, and today I was able to successfully deploy my app again. It does take a lot longer to deploy, but it works. Edit: I tried deploying again after some code changes and now I'm having this same issue again.


angelo-railway

Hey there, First off, sorry for the poor experience. We did trace it to a situation to a host that the low forwarding was impacted. This is now resolved, if you can trigger another build, we can go ahead and debug that with you.

firstmark-dev
PROOP

16 days ago

Hi Angelo - Ive managed to get the build deploy time down but still having super long deploys that crash


noahd
EMPLOYEE

16 days ago

Hey there! Let me take a peek into this


Status changed to Awaiting User Response Railway 16 days ago


noahd
EMPLOYEE

16 days ago

Hey there!
There was something with manual config that I just sorted on our end. Can you try redeploying and let me know if it works!


billdybas
HOBBY

16 days ago

Running into a similar issue with one of my services: 1750d5ee-4c99-487f-b5cc-49c53b0bf73d


Status changed to Awaiting Railway Response Railway 16 days ago


billdybas

Running into a similar issue with one of my services: 1750d5ee-4c99-487f-b5cc-49c53b0bf73d

noahd
EMPLOYEE

16 days ago

Can you provide a link to it? Would be great!


Status changed to Awaiting User Response Railway 16 days ago


noahd

Can you provide a link to it? Would be great!

billdybas
HOBBY

16 days ago


Status changed to Awaiting Railway Response Railway 16 days ago


billdybas

https://railway.com/project/7d34e953-a549-4983-9cf8-7511c221d576/service/1750d5ee-4c99-487f-b5cc-49c53b0bf73d

noahd
EMPLOYEE

16 days ago

Can you abort any ongoing deploy and trigger a new redeploy?


Status changed to Awaiting User Response Railway 16 days ago


noahd

Can you provide a link to it? Would be great!

victor-floriano
HOBBY

16 days ago


Status changed to Awaiting Railway Response Railway 16 days ago


noahd

Can you abort any ongoing deploy and trigger a new redeploy?

billdybas
HOBBY

16 days ago

Done. I tried redeploying twice but they both time out failing on the create container step.



Railway
BOT

15 days ago

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!


We've been addressing infrastructure issues affecting deployments today, and fixes have been applied on our end. Long story short, we expanded capacity and added additional hosts. The build timeouts that you all saw were connected to the inability to find a machine within this time frame. Our monitoring is showing that we are holding up well in the meantime, however, we will continue to monitor this thread if there are issues.


Status changed to Awaiting User Response Railway 15 days ago



Status changed to Awaiting Railway Response Railway 6 days ago





smileart
HOBBY

6 days ago

Same issue here.


innov8si
PRO

6 days ago

same issue here


dezwier
HOBBY

6 days ago

Same issue here :(


korfer
PRO

6 days ago

Same issue. Why no issue elevated in Railway Status page?


niceice5
HOBBY

6 days ago

+1 some issue


laurensvanpoucke
FREE

6 days ago

+1 same issue


multierpio
HOBBY

6 days ago

Same here


puil
HOBBY

6 days ago

Same issue!


omar11n
HOBBY

6 days ago

same here :(



0xpants
FREE

6 days ago

Same here

Attachments


0xpants

Same here

amnesia
HOBBY

6 days ago


amnesia

same...

0xpants
FREE

6 days ago

Managed to successfully deploy, finally


noahd
EMPLOYEE

6 days ago

Howdy!
Was a bug with a part of the deploy flow. Should be good now! Can you try again?


Status changed to Awaiting User Response Railway 6 days ago


Railway
BOT

6 days ago

🛠️ The ticket Container startup failures on some deployments has been marked as triage.


Railway
BOT

6 days ago

Hello!

We've escalated your issue to our engineering team.

We aim to provide an update within 1 business day.

Please reply to this thread if you have any questions!


Loading...