Menu
docker build -t oreng/iojs .
INFO[0000] Get https://index.docker.io/v1/repositories/library/iojs/images: x509: certificate signed by unknown authority. my Dockerfile is
FROM iojs:latest RUN useradd -ms /bin/bash developer WORKDIR /home/developer USER developer Also hub create (using https://github.com/github/hub)
Post https://api.github.com/user/repos: x509: certificate signed by unknown authority 
222
How to resolve Docker x509: certificate signed by unknown authority error. In order to resolve this error, we have to import the CA certificate in use by the ICP into the system keystore. Then, we have to restart the Docker client for the changes to take effect.
So the solution to is simple – install the Root CA certificates on the server. That's it – now the error should be gone. If you don't know the root CA, open the URL that gives you the error in a browser (i.e. Chrome). Click the lock next to the URL and select Certificate (Valid).
509 Certificate Signed by Unknown Authority” error is that you've attempted to use a self-signed certificate in a scenario that requires a trusted CA-signed certificate. Most of the examples we see in the field are self-signed SSL certs being installed to enable HTTPS on a website.
As mentioned in crypto/x509/root_unix.go, Go (which is what Docker uses) will check CA certificates in
"/etc/ssl/certs/ca-certificates.crt", // Debian/Ubuntu/Gentoo etc. "/etc/pki/tls/certs/ca-bundle.crt", // Fedora/RHEL "/etc/ssl/ca-bundle.pem", // OpenSUSE "/etc/ssl/cert.pem", // OpenBSD "/usr/local/share/certs/ca-root-nss.crt", // FreeBSD/DragonFly "/etc/pki/tls/cacert.pem", // OpenELEC "/etc/certs/ca-certificates.crt", // Solaris 11.2+ Make sure those files are available and not corrupted.
There can be also sporadic issue with the CDN, as in this comment:
because now it works :+1: . It must be a amazon edge isssue
The last thread also includes the following check:
The user reporting the issue either has non of those files or those files don't include the
rapidsslcert.
We could ask them to send us those files and check if the certificate is included.
The user may also try this:
openssl s_client -showcerts -verify 32 -connect index.docker.io:443 If that fails, the certificates are missing.
Regarding GitHub, be aware it is under a massive DDoS attack at the moment, which could have other side-effects beside the certificate issue.
151
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
