Skip to content
"Creating containers..." never ends
josegiufrida
OP

10 months ago

Since yesterday, one of my services has been stuck at the "Creating containers..." phase and times out. My original configuration was Nixpacks + Old build environment. I tried Railpack + Metal build environment with the same result. Region: US East (Virginia)

I understand that my problem is the same as the one this user experienced a few hours ago: https://station.railway.com/questions/creating-containers-until-timeout-ba52bb3e

Link to my service: https://railway.com/project/1b07e869-55d0-404b-be01-77f4bc54eedc/service/9e9d6ef4-fd09-41a7-a8df-12d13b1bb489?environmentId=ffa20f2d-161e-4584-8810-448faef46d0b

Solved

17 Replies

10 months ago

Thank you for your report and sorry for the inconvenience, usually that status means a busy queue and it normally resolves after some time, but considering the outages I suppose people are spamming builds.

I will escalate your thread.


10 months ago

!t


10 months ago

This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response medim • 10 months ago


10 months ago

Hey there!

Are you able to trigger a redeploy? Would love to investigate logs as they happen.


Status changed to Awaiting User Response Railway • 10 months ago


Railway
BOT

10 months 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!


10 months ago

Going to attach a ticket so we can track this as well.


Railway
BOT

10 months ago

🛠️ The ticket Container creation error has been marked as triage.


noahd

Hey there! Are you able to trigger a redeploy? Would love to investigate logs as they happen.

josegiufrida
OP

10 months ago

Yes, every time it failed I was able to redeploy.

I just ran a redeploy, but it's still taking too long; I think it will fail again.

It's stuck here, there are no more logs:


Status changed to Awaiting Railway Response Railway • 10 months ago


Anonymous

10 months ago

facing the same issue since yesterday. I just tried create a new Service with the same configuration and it worked


sam-a
EMPLOYEE

10 months ago

Hi josegiufrida - go ahead and try redeploying. I've fixed the issue with your service so it should work. Let us know if there is still an issue.

[email protected] if you run into this issue again, please open a separate thread and let us know the service and we can resolve.


Status changed to Awaiting User Response Railway • 10 months ago


sam-a

Hi josegiufrida - go ahead and try redeploying. I've fixed the issue with your service so it should work. Let us know if there is still an issue. [[email protected]](mailto:[email protected]) if you run into this issue again, please open a separate thread and let us know the service and we can resolve.

josegiufrida
OP

10 months ago

I've already deployed twice since your message, and the problem persists.

Should I switch to Railpack and/or the Metal build environment?


Status changed to Awaiting Railway Response Railway • 10 months ago


10 months ago

Can you try pressing command/ctrl + k and "deploy latest commit" for me?


Status changed to Awaiting User Response Railway • 10 months ago


sunate-tech

10 months ago

Not only not deploying but also we are not able to even look at the logs to get a clue..

This is major for us, we needed to apply a hotfix, impacting 200 user on field.


Status changed to Awaiting Railway Response Railway • 10 months ago


sunate-tech

Not only not deploying but also we are not able to even look at the logs to get a clue.. This is major for us, we needed to apply a hotfix, impacting 200 user on field.

10 months ago

Please open your own thread.


Status changed to Awaiting User Response Railway • 10 months ago


digizeph

10 months ago

Having the same issue now. Cronjob also has been failing since 2026-01-26 and no logs available.


10 months ago

Please open your own thread


Status changed to Solved brody • 10 months ago


noahd

Can you try pressing command/ctrl + k and "deploy latest commit" for me?

josegiufrida
OP

10 months ago

I deployed the latest commit and it worked correctly. Then I make a new commit to my production branch to generate a new build and it worked correctly this time!

I consider the problem solved, thank you very much!


Status changed to Awaiting Railway Response Railway • 10 months ago


Status changed to Solved josegiufrida • 10 months ago


Railway
BOT

9 months ago

✅ The ticket Container creation error has been marked as completed.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...