I am trying to use registry.digitalocean.com for my k8s images.
I’ve created an image, tagged it, logged into the registry successfully (using
doctl registry login) then pushed the image to the registry.
However, when starting the service it’s not creating pods successfully and giving :
Failed to pull image "registry.digitalocean.com/ordering-reg/mongodb-service": rpc error: code = Unknown desc = Error response from daemon Get https://registry.digitalocean.com/v2/ordering-reg/mongodb-service/manifests/latest: unauthorized: authentication required
The pod status is “ImagePullBackOff” and it can’t pull the image.
Does anyone have any idea what might be causing this? My understanding was that if I was logged into the registry OK with doctl, then everything should be authed to pull the image from the registry.
Any help would be gratefully appreciated.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
I had missed out a couple of steps in the guide DigitalOcean Container Registry Quickstart specifically the steps:
In my case, the problem was with “Download Docker Credentials” I used in the UI. I created a k8s secret using that downloaded files, and spent a couple of hours to finally dig out that
doctl registry kubernetes-manifestgives another credentials. Surprisingly, the credentials downloaded from the UI were valid for pushing/pulling from the local machine, but not for pulling images inside the cluster. Strange!
I have follow all the steps and I am getting the same Authentication error. It is driving me crazy! Is someone else having the same problem?