Don’t exactly know what the problem is, but it seems that healthcheck curl commands to https://example.com/ currently fail, probably because of a ssl failure. This causes container that rely on this to fail. Just wanted to let you guys know.
You must log in or register to comment.
Why are you relying on example.com as a health check? To be really blunt about it, if you’re using it then you’ve misconfigured your stuff.
From their docs:
These web services are provided as best effort, but are not designed to support production applications. While incidental traffic for incorrectly configured applications is expected, please do not design applications that require the example domains to have operating HTTP service.
Wat? Why are people health checking their containers by curl’ing example.com and not the service actually running in the container? Did they not understand that they’re supposed to change the curl URL to point at their actual service?
I fixed a test site earlier this week, where someone had decided to test against these for their docker CI.
example.org had an invalid certificate chain.
The certificate of example.com refreshed just a few hours ago, if verification fails on your system check your clock (do time and timezone match?)
Yeah saw that and checked the time, both on the host and container. Both are accurate.
