a year ago
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-628ed97b35b8
1 Replies
a year ago
<#846875565357006878> may be marked as resolved, but issues are still ongoing
a year ago
Wasn't sure if the issue is related, because I'm getting different errors - but some of the issues is from that
a year ago
a year ago
yeah lots of different issues relating to build and deploy
a year ago
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
a year ago
are you on the v2 builder?
a year ago
a year ago
can you tell me more about your setup then?
a year ago
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)
a year ago
would you be okay with adding me to the project?
a year ago
user?
a year ago
email*
a year ago
edit/view?
a year ago
brodyover@gmail.com, edit
a year ago
sent
a year ago
seems like deploys are still screwed
a year ago
well thats interesting
a year ago
did you change anything?
a year ago
no
a year ago
just deploy latest commit
a year ago
well now i have
a year ago
how do you deploy latest commit? ive always been hitting redeploy
a year ago
ctrl / cmd + k -> deploy latest commit
a year ago
okay ill bring this up to the team monday
a year ago
thanks
a year ago
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?
a year ago
ended up working for that one after 5 minutes
a year ago
yea no still broken
a year ago
do the build logs include the same error?
a year ago
just says
We were unable to connect to the registry for this image. If this error persists, please reach out to the Railway team.
a year ago
still same error
a year ago
im so sorry i thought i flagged
a year ago
!t
a year ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response brody • about 1 year ago
a year ago
@christian - container fails to deploy after building fine
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
seems to be fixed as of now
a year ago
This thread has been marked as solved automatically due to a lack of recent activity. Please open a new thread if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 year ago