You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Autoheal didn't seem to be working for me. No logs. Well, the instances that could need to be autohealed rarely failed, which is good news, but made it harder to see if autoheal was working.
It turned out that autoheal: true was the problem. true needs to be quoted: autoheal: "true", as autoheal searches for the lowercase value. Just true gets translated to a True boolean by docker compose, which autoheal doesn't search for.
So....
Should autoheal also accept the True?
Perhaps it is enough to just add a quick note to the README, warning about the quotes?
A short message upon startup (echo "autoheal is running") would personally have helped me to be sure the logging was actually working. I never got any output out of the tool because of the true/True mismatch, but I spend quite some time figuring out whether there was actually something wrong with my logging. That's why the tty: true is in there, for instance.
The text was updated successfully, but these errors were encountered:
Unrelated to the documentation issue... I could probably have omitted the label entirely in my case? I only used it to restrict autoheal to my containers with a health check, preventing autoheal from looking at the non-health-check containers.
Autoheal searches for {"health": "unhealthy"}, so containers without a health check are completely ignored in any case, it seems.
this certainly can be an annoying, I recall docker-compose has got tendencies to do conversions on yml which IMO it shouldn't.
I'd be nice to turn autoheal check to 1/True/true/yes like.
I have a mix of services with only some of them having a health check. So I configured autoheal like this in my
docker-compose.yml
:And the services with healthcheck got the label:
Autoheal didn't seem to be working for me. No logs. Well, the instances that could need to be autohealed rarely failed, which is good news, but made it harder to see if autoheal was working.
It turned out that
autoheal: true
was the problem.true
needs to be quoted:autoheal: "true"
, as autoheal searches for the lowercase value. Justtrue
gets translated to aTrue
boolean by docker compose, which autoheal doesn't search for.So....
True
?echo "autoheal is running"
) would personally have helped me to be sure the logging was actually working. I never got any output out of the tool because of the true/True mismatch, but I spend quite some time figuring out whether there was actually something wrong with my logging. That's why thetty: true
is in there, for instance.The text was updated successfully, but these errors were encountered: