Container Registry Auth not working for private docker images
Hi guys, I created a key from dockerhub and added it to runpod settings "Container Registry Auth". I
- chose a random credential name,
- used my dockerhub username as the username of the credential,
- and used the generated key as the password.
But whenever i try to start a pod with the template, it says credentials not correct. Is there anything that i did wrong? (I did choose the created credential in template)
Solution:Jump to solution
Thank you a lot for the help it worked now! Porbably because i accidentally included blank space when pasting the credential into runpod.
7 Replies
Should I use my email as username in container registry auth ?
seems right, should use your dckerhub user and the api key for password
Yes and my image is from dockerhub. I tried both the sha256 format and the tag format for the private docker hub image, it all failed to authenticate :/ I also tried locally login with the credential generated from Dockerhub and it worked. It just doesn't work when I'm using it in templates for pods. I tried generating two keys one with read only, another one with read&write access. None of them worked on runpod.
should be the tag format
check your username again, or the api key again
if there's no space, extra character, wrong username
Oh ya.. did you use it on the template?
like this
yeah I did
Ill try again tmr
Solution
Thank you a lot for the help it worked now! Porbably because i accidentally included blank space when pasting the credential into runpod.