a year ago
trying to deploy an update and im stuck on creating containers
36 Replies
a year ago
e4267475-b3d8-4b94-9387-03ddffea0a12
a year ago

a year ago
it also killed my old instance before this so now my app has been down for 5+ minutes. 😐
a year ago
probably not a fix for your problem but maybe try a redeploy?
CTRL + K -> deploy latest commit
a year ago
we're at 9 mins now. giving that a try. 😭
a year ago
oh fml thats jsut queued a new one
a year ago
and also I always abort the stuck deployment just in case Railway tries to queue
a year ago
ah
a year ago
same issue
a year ago
we're just stuck.

a year ago
well maybe Railway is just busy ATM
a year ago
… after they take down my existing app 😭
a year ago
that shouldnt happen.
a year ago
yeah that's weird, it should wait for a green deploy before removing any existing one
a year ago
anyway i'll wait for Brody here
cc @Brody
a year ago
a volume is attached to that service, so the deployment does have to be taken down
a year ago
ah that makes sense. though still not sure why its taking 5+ mins to create the container 😭
a year ago
the whole deploy is usually done in that time.
a year ago
looking into it
a year ago
slow deploys
a year ago
oop, hit 10 mins and deploy failed.
a year ago
there's a timeout of 10-15min on deploys, that's normal
a year ago
gotcha
a year ago
@Brody seems the app IS deployed somehow still. its a bot on bluesky i can i still get responses from it.
a year ago
maybe this is why its having trouble creating the container. i wonder if there's a zombie container holding the volume.
a year ago
interesting
a year ago
yeah there is a phantom container
a year ago
👻
a year ago
this was the phantom deploy -
i've removed it, please try redeploying again
a year ago
am i good to use the deploy with latest commit command or should i push a new commit?
a year ago
deploy with latest commit is fine
a year ago
holy shit thats fast
a year ago

a year ago
cache
a year ago
working 🙏
a year ago
!s
Status changed to Solved brody • about 1 year ago