a year ago
I'm having an issue where it's stuck on creating the container for my web app after I made minor updates. Of course, there are no deploy logs, as deployment hasn't happened yet. The build step finished okay. Any advice?
16 Replies
@Stefan I realized after creating my issue that we might have the same issue. Mine is a cron that stopped running. To me, it's not working right now. Could you check if it's working for you rigght now?
https://discord.com/channels/713503345364697088/1259517941599174656
My app eventually built, though I had to redeploy a couple of times and abort the previous deployments. I hope your issue gets resolved soon!
a year ago
Update for y'all @Stefan and @alvar, so we have deployed a possible fix tightening up the scheduling workflow when it comes to build resolution.
The good news is that as of late, we are stately running builds, the problem is that it's eventually consistent, the word eventually doing a lot of work here.
Our founder Cooper is on it as we speak.
a year ago
Much thanks! I'm noticing this issue as well.
a year ago
just now you have experienced this issue again?
a year ago
Correct
a year ago
I've done a few pushes today. Most of them have worked (though the build process was slow). Now it's suck on "Create container"
a year ago
Doing a re-deploy seems to have worked for the moment though.
a year ago
incident called -> <#846875565357006878>
a year ago
Still not fixed I don't think.
a year ago
team is still working on a fix for this, please check
for updates
a year ago
this was marked as resolved, let us know if you experience this issue again!
a year ago
I am experiencing the same issue as well... I don't think https://railway.instatus.com/clyotu5or116647hioqmpu9hfo5 is fully fixed?
Experiencing issues on project b47bb4e5-34bf-4b2e-a98d-a7f8754d74e1
Status changed to Awaiting Railway Response railway[bot] • 12 months ago
a year ago
Circling back here to confirm that a fix has gone out. @mocha let us know if you are still experiencing issues.
Status changed to Awaiting User Response railway[bot] • 12 months ago
a year ago
Seeing this same issue on my end on project 721c710f-bc5e-4674-a174-24dac0f911be
Stuck on the "Creating Containers" step for over 11 minutes after updating the DATABASE_URL env var to an external Postgres instance. When I switch back to a Railway-managed Postgres and link my server to the database via reference variable the container build step drops substantially.
a year ago
Same for us.
66509111-e78e-46e3-a03c-67f7cd5f3e31
a year ago
please cancel and redeploy
a year ago
Please simply allow the system to retry and deploy your instance. Don't cancel and redeploy these
We're having a bit of sag in our registry. Continued retries will simply make it worse.
We're looking into this as our number one priority this week
a year ago
Unfortunately waiting does not work, only redeploying and aborting stucked deployment :/
a year ago
I'm also facing this issue so would be good to get this fixed.
a year ago
+1
a year ago
I am currently facing the same issue 40mins on creating containers and when I try to abort I get a message saying "failed to fetch"
a year ago
Same here. Very frustrated with all the problems I've experienced since migrating to Railway. Your service is very unreliable.
a year ago
Still not resolved
a year ago
Stuck on creating containers
a year ago
issue still happening
a year ago
For those with this issue, could you please leave a link to your deployment's URL so we can investigate further?
a year ago
Same issue here
Not sure if others will find solutions here, but I'm trying to switch my region
a year ago
Did you had success getting the services live?
I did get the services live, but I would 100% not do it. My MongoDB data did not replicate correctly
a year ago
cc @Ray for viz
6 months ago
happening to me today
Status changed to Awaiting Railway Response railway[bot] • 6 months ago
Status changed to Awaiting User Response railway[bot] • 6 months ago
6 months ago
!s
Status changed to Solved brody • 6 months ago