docker-credential-helpers: docker login Succeeded, docker pull failed
I use pass
docker login Succeeded:
# docker login
Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.
Username: liaolinrong
Password:
Login Succeeded
but when docker pull a private image, is error:
docker pull liaolinrong/centos:7.3.1611
Error response from daemon: pull access denied for liaolinrong/centos, repository does not exist or may require 'docker login'
/root/.docker/config.json :
# cat /root/.docker/config.json
{
"auths": {
"https://index.docker.io/v1/": {}
},
"HttpHeaders": {
"User-Agent": "Docker-Client/18.09.7 (linux)"
},
"credsStore": "pass"
}
os:
# cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
# uname -a
Linux VM_0_6_centos 3.10.0-862.el7.x86_64 #1 SMP Fri Apr 20 16:44:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
docker version:
# docker -v
Docker version 18.09.7, build 2d0083d
About this issue
- Original URL
- State: open
- Created 5 years ago
- Reactions: 16
- Comments: 27
This is still an active issue, it completely prevents us of using this provider
does your GPG key have a passphrase?
if so, can you try doing this first:
if you are using “hub.docker.com” make sure to have enough private docker repository in your docker hub account. it seems you can create a private image but you can not pull the image when you exceed the private repository limits.
I still get this error on Windows. I can login Successfully and the when I inspect the docker/config.json I see the Auths object but no password within it.
it worked for me after run apt-get update .
The same issue for me. @maxthomas workaround with
not working on Ubuntu 18.04. It starts after my GPG key expired. I’ve updated it in pass configuration and removed all stored data, but it still login success, but can’t pull images.
FWIW, changing credentials to a new PAT did the trick for me.
This works for me.
I get pull rate limit error when pulling images from docker hub, even after login. But this workaround works for me.
This solved it for me on ubuntu