<#846875565357006878> 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?

brodyover@gmail.com, 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 monday

thanks

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

@christian - container fails to deploy after building fine

seems to be fixed as of now