We were unable to connect to the registry for this image.
Sorry I'm going to be a thorn here. I've asked a few times for assistance on this but I keep seeing issues that are within the user's power to resolve being addressed but I am, unfortunately, stuck on this without any recourse.
For the last 37 hours I cannot deploy a service because I get this error after the built image is pushed to the registry:
========================= Container failed to start ========================= We were unable to connect to the registry for this image. If this error persists, please reach out to the Railway team.So I am doing exactly that. Am I asking for support somehow incorrectly? Any help would be very much appreciated in resolving this. Project ID: 457de422-82f4-486d-b6e4-0f538f57c8e6 P.S. I cannot close my other support requests but I would if able.
6 Replies
Project ID:
457de422-82f4-486d-b6e4-0f538f57c8e6Going to need more details, what build provider are you using?
Not sure what is meant by "provider" but it is a dockerfile and I do not have the "New Builder Environment" set.
Are there any other details you need?
what is your service source?
My code on github
Ok I've been trying several things and it looks like the permissions on my entrypoint weren't set correctly. The error message in the logs ("unable to connect to the registry") seems misleading because that does not seem to have been the issue.
This can be closed, though.
I'll keep this open because this error message should be corrected