Error response from daemon: Get "https://registry.example.com/v2/": x509: certificate signed by unknown authority
Docker doesn't trust the registry's certificate
Seen in docker pull, docker push, docker login, Docker Desktop
The Docker daemon could not chain the registry's certificate to a CA it trusts.
Common causes
- A private registry uses a certificate from an internal CA or a self-signed certificate.
- A corporate proxy re-signs HTTPS traffic to Docker Hub or other registries.
- The registry does not send its intermediate certificate.
How to fix it
- Trust the CA for that registry: place it at /etc/docker/certs.d/registry.example.com:5000/ca.crt (the port is part of the folder name if used).
- Or add the CA to the host trust store (update-ca-certificates) and restart Docker; on Docker Desktop, add it to the OS keychain or certificate store.
- Serve the full chain from the registry. Avoid insecure-registries, which disables verification.
Got a different message? Paste it into the error explainer.
Related errors
- fatal: unable to access '...': SSL certificate problem: unable to get local issuer certificate · Git can't verify the server's certificate
- npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY · npm can't verify the registry's certificate
- npm ERR! code SELF_SIGNED_CERT_IN_CHAIN · npm sees an untrusted root certificate
- fatal: unable to access '...': Could not resolve host: github.com · Git can't resolve the remote's hostname
- error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 · The push is larger than the server or proxy accepts
- error: RPC failed; curl 18 transfer closed with outstanding read data remaining · The connection dropped during a git transfer
- fatal: the remote end hung up unexpectedly · The Git server closed the connection
- kex_exchange_identification: Connection closed by remote host · The SSH server closed the connection before the handshake
- Permission denied (publickey) · The server rejected every SSH key you offered
- Host key verification failed. · SSH couldn't confirm the server's identity
- WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! · The server's SSH host key is different from last time
- Unable to negotiate with 203.0.113.10 port 22: no matching host key type found. Their offer: ssh-rsa · The server only offers an old host key type