"healtcheck" parameter does not behave in an idempotent manner about ansible-podman-collections HOT 3 CLOSED

Thanks for reporting this. Can you please elaborate - what is the use case of setting healthcheck command to none?

from ansible-podman-collections.

Beside it being a feature of podman itself, (see here) I wanted to disable the healtcheck for one of my containers because it was causing a lot of log messages with the contents of container exec_died ... that comes from the healtcheck.

This is somewhat related to this issue where someone also asked for a log level feature: containers/podman#17856.

An example of the amount of logging that gets aggregated is here (left before I disabled the healtcheck and right after I set it to none)

So for me why I'm disableing this is I don't need that healtcheck (I have my own monitoring) and to reduce disk IO. But honestly I don't think my reasoning should be entirety relevant, surly someone at some point has a better reason to use this feature and I think it's nice if that is supported (with it being an intended feature after all 😄 )

from ansible-podman-collections.

@idelsink #745 should fix all for you. Please feel free to reopen if it still has an issue or you discover a new one.

from ansible-podman-collections.