1:45 a.m.
Hey Brian,
Thanks for reaching out. There is a very recent upstream issue for that:
https://github.com/containers/podman/issues/8615
For now, there's nothing to worry about. systemd decided to gently
deprecate KillMode=none as it was a continuous source of confusion and
bugs. We will change none to another mode. I plan to do that before Podman
3.0 early next year.
I pulled in Michal from the systemd team who may elaborate a bit how and
when the final deprecation will look like.
Kind regards,
Valentin
On Wed, Dec 9, 2020 at 4:05 AM Brian Fallik <bfallik(a)gmail.com> wrote:
Hi,
I've been happily deploying my container services in podman using
podman-generate-systemd
<http://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html> unit
files. Recently I noticed a scary warning in journald:
XXX systemd[1]: /etc/systemd/system/container-xxx.service:21: Unit
configured to use KillMode=none. This is unsafe, as it disables systemd's
process lifecycle management for the service. Please update your service to
use a safer KillMode=, such as 'mixed' or 'control-group'. Support for
KillMode=none is deprecated and will eventually be removed.
This KillMode line was generated by Podman.
I don't have any reason to believe that KillMode=none isn't as expected.
Podman and systemd are tracking and killing my container processes
correctly as far as I can tell. But the final sentence made me wonder if my
unit files will suddenly stop working after a future version of systemd
removes support for KillMode=none.
A quick Google search and scan of Podman Github issues didn't turn up
anything related so I thought I'd ask this group.
Thanks,
brian
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io