4 months ago
Error Log:
=========================Container failed to start
=========================
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.
Looks like Railway does not accept multiple input line in both "Pre-deploy Command" and "Custom Start Command".
This is the code I should deploy (WAHA PLUS, in place of {KEY} I've put my personal Docker Hub Key):
docker login -u devlikeapro -p {KEY}
docker pull devlikeapro/waha-plus
docker logout
I tried this:
1st attempt:
docker pull devlikeapro/waha-plus
docker logout
Pre-deploy Command:
sh -c "docker login -u devlikeapro -p {KEY} && docker pull devlikeapro/waha-plus && docker logout"
Custom Start Command:
2nd attempt:
Pre-deploy Command:
sh -c "docker login -u devlikeapro -p {KEY} && docker pull devlikeapro/waha-plus"
Custom Start Command:
docker logout
3rd attempt:
Pre-deploy Command:
sh -c "docker login -u devlikeapro -p dckr_pat_0RngnV4-hLRVhfcm25JjwZ3hJB4 && docker pull devlikeapro/waha-plus"
Custom Start Command:sh -c "docker pull devlikeapro/waha-plus && docker logout"
Always the same error... can anybody help me?
(I'm not expert of docker...)
2 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 stuck at this error "unable to connect to the registry for this image"
🧵 Docker Image "We were unable to connect to the registry for this image"
If you find the answer from one of these, please let us know by solving the thread!
Status changed to Awaiting User Response Railway • 4 months ago
3 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 • 3 months ago