Extremely long container deployment times + inconsistent build statuses
six
HOBBYOP

2 years 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

Solved

36 Replies

brody
EMPLOYEE

2 years ago

<#846875565357006878> may be marked as resolved, but issues are still ongoing


six
HOBBYOP

2 years ago

Wasn't sure if the issue is related, because I'm getting different errors - but some of the issues is from that


six
HOBBYOP

2 years ago

1261166047042736000


brody
EMPLOYEE

2 years ago

yeah lots of different issues relating to build and deploy


six
HOBBYOP

2 years 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

1261383181408538600


brody
EMPLOYEE

2 years ago

are you on the v2 builder?


six
HOBBYOP

2 years ago

1261385084628631600


brody
EMPLOYEE

2 years ago

can you tell me more about your setup then?


six
HOBBYOP

2 years 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)

1261524425233399800


brody
EMPLOYEE

2 years ago

would you be okay with adding me to the project?


six
HOBBYOP

2 years ago

user?


six
HOBBYOP

2 years ago

email*


six
HOBBYOP

2 years ago

edit/view?


brody
EMPLOYEE

2 years ago

brodyover@gmail.com, edit


six
HOBBYOP

2 years ago

sent


six
HOBBYOP

2 years ago

seems like deploys are still screwed


brody
EMPLOYEE

2 years ago

well thats interesting


six
HOBBYOP

2 years ago

did you change anything?


brody
EMPLOYEE

2 years ago

no


brody
EMPLOYEE

2 years ago

just deploy latest commit


brody
EMPLOYEE

2 years ago

well now i have


six
HOBBYOP

2 years ago

how do you deploy latest commit? ive always been hitting redeploy


brody
EMPLOYEE

2 years ago

ctrl / cmd + k -> deploy latest commit


brody
EMPLOYEE

2 years ago

okay ill bring this up to the team monday


six
HOBBYOP

2 years ago

thanks


six
HOBBYOP

2 years 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?


six
HOBBYOP

2 years ago

ended up working for that one after 5 minutes


six
HOBBYOP

2 years ago

yea no still broken


brody
EMPLOYEE

2 years ago

do the build logs include the same error?


six
HOBBYOP

2 years 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.


six
HOBBYOP

2 years ago

still same error


brody
EMPLOYEE

2 years ago

im so sorry i thought i flagged


brody
EMPLOYEE

2 years ago

!t


brody
EMPLOYEE

2 years ago

This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response brody over 1 year ago


brody
EMPLOYEE

2 years ago

@christian - container fails to deploy after building fine


Thank you for escalating, Brody! We're looking into this!


Status changed to Awaiting User Response Railway over 1 year ago


six
HOBBYOP

a year ago

seems to be fixed as of now


Railway
BOT

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 over 1 year ago


Loading...