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.
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.
Thank you so much for your detailed answer. That brought me up to speed. I just never questioned it and, as you said, assumed that it was to test network connectivity.
It also finally explains the issues with those containers I kept having every few months. It always fixed itself before I had the time to actually look into it, but it has always been bugging me. This time I was able to actually catch it.
I’ll update the health checks to the proper URL im using, or should I use localhost:port?
Anyway, thanks again!
the healthcheck URL should point to some HTTP API that the container makes available, so it should point to the container.
in place of localhost should be the container’s name, and port should be the port the container exposes as the web server. some services, like Jellyfin, have a specific webpage path for this purpose: https://jellyfin.org/docs/general/post-install/networking/advanced/monitoring/
and others, like gitea, hide the fact well that they have a health check endpoint, because its not mentioned in documentation: https://github.com/go-gitea/gitea/pull/18465
but check if docker’s way of doing healthchecks produces a lot of spam in the system log, in which case you could choose to just disable health checking, because it would push out useful logs
Thanks for explaining it to me in a simple manner, I will update the url accordingly!