x509: certificate signed by unknown authority about distribution-library-image HOT 10 CLOSED

#28616 ×509:

from distribution-library-image.

Looks like the daemon does not trust the registry. Did you add the registry CA to docker certs?

from distribution-library-image.

Also, please open this issue in docker/docker or docker/distribution.

from distribution-library-image.

I had this problem on the past trying run a docker-machine in virtualbox. I figure out that was 'the man of midle' in this case my proxy that signing every single package that it sends to me. Then I just provide the proxy certificate copying my proxy certificate to /var/lib/boot2docker/certs in docker-machine. However, I don't know how do the same To docker swarm. When I try to run swarm. I am having the follow error:

2017/01/18 22:16:21 Post https://discovery.hub.docker.com/v1/clusters: x509: certificate signed by unknown authority

There is a way to past my proxy certificate when I run the swarm node. I have tried to map my local cert with -v /home/docker-host/.docker/:/certs, but this didn't work.

from distribution-library-image.

I have the same problem. I tried to change the certificated name from
/etc/docker/certs.d/registryname:5000/ca.crt to/etc/docker/certs.d/registryname:5000/domain.crt but it didn't work

from distribution-library-image.

same problem with 16.04.
x509: certificate signed by unknown authority

from distribution-library-image.

Try and add your corp proxy's certificate both at OS and docker level.
Try and setup your "/etc/docker/certs.d//" directory/files (for me it was necessary for "docker search" to work).
You may eventually specify which certificate location dockerd will use by adding a "tlscert" entry in your /etc/docker/daemon.json file. Use the one curl uses.
These 3 points solved the issue for me.

from distribution-library-image.

Now added the corp proxy certificate in /etc/ssl and /etc/.. pki/anchors/ and it fixed the problem.

from distribution-library-image.

Any solution for the same problem in windows 10, Docker for windows??

from distribution-library-image.

Try and add your corp proxy's certificate both at OS and docker level.
Try and setup your "/etc/docker/certs.d//" directory/files (for me it was necessary for "docker search" to work).
You may eventually specify which certificate location dockerd will use by adding a "tlscert" entry in your /etc/docker/daemon.json file. Use the one curl uses.
These 3 points solved the issue for me.

it works!

from distribution-library-image.