Extremely long container deployment times + inconsistent build statuses
Deployments are taking over 10 minutes - the build step takes a minute or so, and gets stuck on creating containers. In addition, I've made a few seperate services that point to the same repository, but some of these services aren't even able to build properly even with the same configuration as another that builds properly. Some of the builds also just quit with the error
We were unable to connect to the registry for this image.
Project ID: 4a7d8d53-a35f-4e04-9170-628ed97b35b827 Replies
Project ID:
4a7d8d53-a35f-4e04-9170-628ed97b35b8#🚨｜incidents may be marked as resolved, but issues are still ongoing
Wasn't sure if the issue is related, because I'm getting different errors - but some of the issues is from that
yeah lots of different issues relating to build and deploy
assuming this is unrelated to the build issues, why is this happening? shouldnt railway use the Dockerfile (exact name)? i tried with
RAILWAY_DOCKERFILE_PATH as well to Dockerfile.autosetup and that spat out the same error
are you on the v2 builder?
can you tell me more about your setup then?
https://github.com/6ixfalls/railway-temporal
one of the services runs Dockerfile.autosetup, I want the other 3 to run the base Dockerfile (which should be the default)
would you be okay with adding me to the project?
user?
email*
edit/view?
[email protected], edit
sent
seems like deploys are still screwed
well thats interesting
did you change anything?
no
just deploy latest commit
well now i have
how do you deploy latest commit? ive always been hitting redeploy
ctrl / cmd + k -> deploy latest commit
okay ill bring this up to the team mondaythanks
made another project for a different thing, deploys worked fine up until now - either based on load or something to do with the repository/railway project?
ended up working for that one after 5 minutes
yea no still broken
do the build logs include the same error?
just says
We were unable to connect to the registry for this image. If this error persists, please reach out to the Railway team.still same error
im so sorry i thought i flagged
!t
New reply sent from Help Station thread:
This thread has been escalated to the Railway team.You're seeing this because this thread has been automatically linked to the Help Station thread.
@Christian - container fails to deploy after building fine
New reply sent from Help Station thread:
Thank you for escalating, Brody! We're looking into this!You're seeing this because this thread has been automatically linked to the Help Station thread.
Solution
seems to be fixed as of now