Deploy failed: unable to connect to the registry for this image

a year ago

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.

https://github.com/upay-project/railway-prometheus

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

Solved

7 Replies

Hi there, it looks like you deleted the service you reported issues with. Are you still experiencing problems?


Status changed to Awaiting User Response Railway about 1 year ago


christian

Hi there, it looks like you deleted the service you reported issues with. Are you still experiencing problems?

a year ago

Yes. This is a public repository, so you can try it yourself. It is still facing this problem.


Status changed to Awaiting Railway Response Railway about 1 year ago


a year ago

I have solved this problem.


Thank you for the update. This was a permission issue with your Dockerfile?


Status changed to Awaiting User Response Railway about 1 year ago


a year ago

Yeah. Apologies for taking up your time with such a simple issue. However, I would suggest improving the error messages. Users find it challenging to deduce anything about the inability to execute the Dockerfile from a message like “unable to connect to the registry for this image.”


Status changed to Awaiting Railway Response Railway about 1 year ago


Railway
BOT

a year ago

An internal ticket has been attached to this thread. Updates will be relayed in this thread, so keep an eye out!

Status changed to In Progress Railway about 1 year ago


Thank you for the feedback. We've created a ticket to review the error message.


Status changed to Awaiting User Response Railway about 1 year ago


Status changed to Solved christian about 1 year ago


Railway
BOT

a year ago

Update: An internal ticket linked to this thread has been changed to Completed.

Status changed to Awaiting Railway Response Railway about 1 year ago


Following up to let you know that this error message has been improved with more granular messages for cases when there aren't execute permissions on the start command (see the attached screenshot).

Attachments


Status changed to Awaiting User Response Railway about 1 year ago


Railway
BOT

7 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 7 months ago


Loading...