Exporter not working when keepalived container init doesn't handle keepalived signals about keepalived-exporter HOT 2 CLOSED

Sorry for the very long delay. We'll investigate soon.

@clwluvw Could you please investigate this issue?

from keepalived-exporter.

We discussed that internally and agreed that this is the used keepalived image issue that is not running keepalived daemon as a pid 1 (which is the correct behavior in container runtime). So trying to support that bad practices would put us in a hole of dirty if/else which makes the project unmaintainable as an open source project (as it's going to accept source code changes from others).

As the mentioned image repo is deprecated (hasn't been updated for two years) you probably can build your own image (by replaying what the repo does or just simply installing keepalived from an alpine base which is not very outdated - e.g. https://github.com/mehdy/keepalived-exporter/blob/master/deployments/dev/keepalived.Dockerfile).
Also forking the repo and adding the ability on your own is also an option.

from keepalived-exporter.