No yubikey found, using alternative key storage: no library found

General
1

I already posted regarding my issue

docker -D  run -d -p 3080:3080 --name mern-stack mern-image:1.0
DEBU[0000] reading certificate directory: /home/miki/.docker/tls/notary.docker.io 
DEBU[0001] No yubikey found, using alternative key storage: no library found 
DEBU[0001] Making dir path: /home/miki/.docker/trust/tuf/docker.io/library/mern-image/changelist 
DEBU[0008] received HTTP status 401 when requesting root. 
docker: you are not authorized to perform this operation: server returned 401.
See 'docker run --help'.

Why is docker looking for yubikey?

2

I assume you mean in this topic

I asked about notary in the other topic and your answer was:

Now your log shows

If it is caused by an old config that you don’t need anymore, and if you don’t have anything that you want to keep from the client config, you can remove the /home/miki/.docker/. IF you don’t want to do that, you should definitely check the client config json

/home/miki/.docker/config.json

It could be a wrong authentication setting, but again, I have never used Notary so all I can suggest is checking the credStore parameter and maybe auths

3

Hi,

Thanks for help.
OK let’s delete .docker

cd ~/.docker
bash: cd: /home/miki/.docker: No such file or directory

when I run

docker -D run -d --name mern-stack mern-image:2.0
DEBU[0000] reading certificate directory: /home/miki/.docker/tls/notary.docker.io 
DEBU[0000] No yubikey found, using alternative key storage: no library found 
DEBU[0000] Making dir path: /home/miki/.docker/trust/tuf/docker.io/library/mern-image/changelist 
DEBU[0001] received HTTP status 401 when requesting root.

.docker will be recreated again

Take a look at tree structure

~/.docker$ tree
.
└── trust
    ├── private
    └── tuf
        └── docker.io
            └── library
                └── mern-image
                    ├── changelist
                    └── metadata

I do not have config.json.

4

I was able to reproduce the issue. You must have enabled content trust possibly in a bashrc file. Can you run the container this way?

export DOCKER_CONTENT_TRUST=0
docker -D  run -d -p 3080:3080 --name mern-stack mern-image:1.0

With content trust enabled you need to sign images. I realized that mern-image is not an official image from Docker Hub but one that you have built yourself. If you want to learn more about content trust you can read about it in the documentation: