Looks like it's functional again:
Sending build context to Docker daemon
Step 0 : FROM ubuntu:trusty
511136ea3c5a: Pull complete
index.docker.io was serving an expired certificate
21–26 of 26 posts
Re: index.docker.io was serving an expired certificate
#22For anyone interested. If you are running Nagios/Sensu, then I highly suggest using one of the ssl check plugins [1, 2, 3], which will give you a heads up about these types of these before they happen. Then the onus is not on you to check some calendar/spreadsheet for expiring certs. Same goes for domains [4, 5]. When you are looking after tons of services, ssl certs, and domains, it is inevitable that things will sl…
Every CA I've ever used sends reminder emails. The problem is they are probably going to some un-read administrative email address.
I can't speak to what certificate was in place before, but now there seems to be a wildcard certificate installed that isn't expired.
If the old certificate was also a wildcard certificate, it stands to reason that even if the CA sent a reminder email, this particular front end could have been overlooked.
Re: index.docker.io was serving an expired certificate
#23SSL is the wrong security mechanism to be relying on here.
If you want immutable deploys, what you actually want is a hash over the content.
When you embed a hash over the content in your deploy script, you guarantee true immutable deploys: everything will be exactly what you ask for, forever. You're not beholden to SSL for security; you're not beholden to anyone maintaining the servers to "be a good citizen". You just have guarantees.
Use a hash over your content.
Re: index.docker.io was serving an expired certificate
#24SSL is the wrong security mechanism to be relying on here. If you want immutable deploys, what you actually want is a hash over the content. When you embed a hash over the content in your deploy script, you guarantee true immutable deploys: everything will be exactly what you ask for, forever. You're not beholden to SSL for security; you're not beholden to anyone maintaining the servers to "be a good citizen". You ju…
I'm not sure what this has to do with, for example, being able to query the docker hub search API?
Re: index.docker.io was serving an expired certificate
#25SSL is the wrong security mechanism to be relying on here. If you want immutable deploys, what you actually want is a hash over the content. When you embed a hash over the content in your deploy script, you guarantee true immutable deploys: everything will be exactly what you ask for, forever. You're not beholden to SSL for security; you're not beholden to anyone maintaining the servers to "be a good citizen". You ju…
I'm not sure what this has to do with, for example, being able to query the docker hub search API?
Very little.
It has everything, however, to do with all of the images served from that domain which people use to execute software on their machines.
Re: index.docker.io was serving an expired certificate
#26For anyone interested. If you are running Nagios/Sensu, then I highly suggest using one of the ssl check plugins [1, 2, 3], which will give you a heads up about these types of these before they happen. Then the onus is not on you to check some calendar/spreadsheet for expiring certs. Same goes for domains [4, 5]. When you are looking after tons of services, ssl certs, and domains, it is inevitable that things will sl…
On Windows (if you're not using Nagios), PA Server Monitor can do this for you.
http://www.poweradmin.com/help/sm_5_7/monitor_web_page.aspx
There really is no reason to be surprised by an expiring cert any more.