a year ago
I've been getting this error for hours:
"We were unable to connect to the registry for this image. If you are using a private image, please make sure your credentials are valid. If this error persists, please reach out to the Railway team."
The image builds and deploys fine locally, and I'm not using a private image.
Some extra debug info would be great!
Also, the health endpoint was always failing, even on a working image earlier in the day, so I needed to disable it. It works on identically setup projects. Maybe it is related?
Thank you!
James
ⓘ Deployment information is only viewable by project members and Railway employees.
3 Replies
a year ago
From our internal logs -
open executable: Permission denied: OCI permission denieda year ago
Thank you! It was just the executable permission bits on my startup script. It would be great to have this sort of extra logging info in the console somewhere; maybe under a separate "internal build logs" tab, or just under build or deploy.
a year ago
This wasn't exposed to the user in the interest of not exposing any potential internal log of our system during the deploy process but its seems like we are being a bit too strict on that.
Glad this helped!
Status changed to Solved brody • over 1 year ago