x509: certificate has expired or is not yet valid

[cinterloper]

https://index.docker.io/ has an expired SSL cert

[cinterloper]

root# docker pull registry
Pulling repository registry
FATA[0000] Get https://index.docker.io/v1/repositories/library/registry/images: x509: certificate has expired or is not yet valid

[intlabs]

Can confirm :(

[chriskinsman]

Arggh. Blocking

[st3wart]

Same problem. Public or private registries.

[tiborvass]

We are aware of the situation and are working on it as fast as we can. FYI for next time please send an email to support@docker.com, this github is about the open source project, not the Hub :) Thanks!

We'll be updating https://status.docker.com/ throughout the events.

[bobbytables]

For anyone else that runs into this and stumbles across this page, this fixes it for me:

boot2docker ssh
sudo ntpclient -s -h pool.ntp.org

Hope this helps.

[endeepak]

+1 for @bobbytables solution. It worked for me on mac.

[lukabirsa]

+1 for @bobbytables solution. Worked for me.

[DyegoCosta]

+1 for @bobbytables solution :)))

[maximderbin]

+1 for @bobbytables solution :)))

[roylanceMichael]

+1 for @bobbytables solution as well (btw, love the xkcd reference). This worked on Windows like a charm (which makes sense, as the VM for mac and windows is similar I believe)

[danstn]

Thanks, @bobbytables. Worked for me as well.

[resoliwan]

+1 for @bobbytables solution :)))

[sabya08]

+1 for @bobbytables solution

[ruairiquinn]

Another +1 for @bobbytables solution

[pditommaso]

+1 for @bobbytables solution 👏

[asampat3090]

👍 for @bobbytables solution

[centerorbit]

I had a similar issue using the native Docker for Mac. It was giving me the same error.

@bobbytables solution implied that the clock drifted, and so the SSL connection could not be properly established. I've seen this before with VMs when the host computer is put to sleep, the VM time can drift from realtime.

Native Docker for Mac still has a VM, it's just a very thin Linux Hypervisor, yet still susceptible to clock drift. Simply restarting docker on the host machine fixed the problem.

[itsNikolay]

• MacOS users that still getting the issue, try to restart Docker:

- For self signed certificates:

Append domain.crt to /etc/ssl/certs/ca-certificates.crt
with $ cat /certs/domain.crt > /etc/ssl/certs/ca-certificates.crt
More information here: https://forums.docker.com/t/adding-self-signed-certificates/9761/18

[kvaps]

Hi, I got same error. But I found out where is problem.

If your system time is fine, try to flush your dns-server cache first.
If it have big (>512 bytes) cached answer, it can be problem for iterpret by go dns library.
See: golang/go#21160
And if it can't get answer at first time, it will ask your search domain next time.

PS: I had same problem when I run kubeadm init:

unable to get URL "https://storage.googleapis.com/kubernetes-release/release/stable-1.7.txt": Get https://storage.googleapis.com/kubernetes-release/release/stable-1.7.txt: x509: certificate has expired or is not yet valid

[mostafaelsayyad]

if u r using centos then check machine date time, adjust it to the current time.
this worked for me.

[viay]

@itsNikolay Thanks. It worked for me

[dsw0214]

@mostafaelsayyad Thanks. It worked for me

[jaakkouu]

if u r using centos then check machine date time, adjust it to the current time.
this worked for me.

This fixed my problem on CentOS 6