3 ms·
Systemd struggles with this as well. While a service can easily tell you if it's "up", sometimes the only way to determine if it's "available" is to check. Keep
by dumpsterdiver 6y ago
Systemd struggles with this as well. While a service can easily tell you if it's "up", sometimes the only way to determine if it's "available" is to check. Keep in mind that the sentinel for any given service will be different. If you think about it, how could any external monitoring service determine when a service under it's purview is available without actually checking?
Maybe it already has something like this, but I feel like systemd could provide an API endpoint for applications to send a simple status when they are "ready" - at which point it would be up to the developers to provide that at the right time.
- lloeki 6y agoAm I understanding this wrong or is HEALTHCHECK supposed to enable that? https://docs.docker.com/engine/reference/builder/#healthcheck https://docs.docker.com/engine/reference/builder/#healthchec...
- joana035 6y agoHere you go: https://www.freedesktop.org/software/systemd/man/systemd-notify.html https://www.freedesktop.org/software/systemd/man/systemd-not...
- dumpsterdiver 6y agoFrom the link: "systemd-notify may be called by daemon scripts to notify the init system about status changes. It can be used to send arbitrary information, encoded in an environment-block-like list of strings. Most importantly, it can be used for start-up completion notification." Perfect. Thank you!
- joana035 6y agoYou're welcome :)