Why no OpenRC(Alpine) support or dedicated little service? #27306
Unanswered
senpro-ingwersenk
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Because most people use systemd so the amount of people caring would be quite low if you also consider most don't use healthchecks. I it was just recently that someone contributed something to address it, #27033
see #27033 (review) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I just fell into an unexpected, really "dumb" pitfall that properly confused me.
When a container defines
HEALTHCHECKs, Podman would schedule them to be looked after. Well - it does do that, but only with SystemD and not with OpenRC, which is what Alpine uses.My collegue contacted me, asking me why his containers were stuck in "starting" and it took me way too long to figure this one out. For the time being, I have just done a little cronjob - but that feels like such a hack, seriously.
On Alpine, the
podman-openrcpackage starts a small Podman service (podman --start --respawn-delay 2 --respawn-max 5 --respawn-period 1800 --user root /usr/bin/podman -- system service --time 0) - and I am curios, why this one couldn't also periodically run healthchecks too?Like, I know that Podman is largely "systemd-oriented" - for the lack of a better term - but this still feels like a missing feature.
So, aside from a crontab "hack", is there actually a better solution to this? And, why exactly is this not implemented? Don't get me wrong, I am genuenly curious (and pretty baffled simultaneously, kinda).
Thanks, and kind regards! :)
Beta Was this translation helpful? Give feedback.
All reactions