summaryrefslogtreecommitdiff
path: root/contrib
diff options
context:
space:
mode:
authorValentin Rothberg <rothberg@redhat.com>2020-08-13 12:53:28 +0200
committerMatthew Heon <matthew.heon@pm.me>2020-08-20 12:16:52 -0400
commitcb4c5fc9c262f14c935e843224ee80e098d58224 (patch)
tree4bb05014e72870a6c4bc6f54fdedc015254bea6a /contrib
parent5e50ba3ecbdd738679849d7a86fef0c4ab7f109d (diff)
downloadpodman-cb4c5fc9c262f14c935e843224ee80e098d58224.tar.gz
podman-cb4c5fc9c262f14c935e843224ee80e098d58224.tar.bz2
podman-cb4c5fc9c262f14c935e843224ee80e098d58224.zip
podman.service: use sdnotiy
Commit 2b6dd3fb4384 set the killmode of the podman.service to the systemd default which ultimately lead to the problem that systemd will kill *all* processes inside the unit's cgroup and hence kill all containers whenever the service is stopped. Fix it by setting the type to sdnotify and the killmode to process. `podman system service` will send the necessary notify messages when the NOTIFY_SOCKET is set and unset it right after to prevent the backend and container runtimes from jumping in between and send messages as well. Fixes: #7294 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'contrib')
-rw-r--r--contrib/systemd/system/podman.service3
1 files changed, 2 insertions, 1 deletions
diff --git a/contrib/systemd/system/podman.service b/contrib/systemd/system/podman.service
index c8751168d..e14bbe078 100644
--- a/contrib/systemd/system/podman.service
+++ b/contrib/systemd/system/podman.service
@@ -6,5 +6,6 @@ Documentation=man:podman-system-service(1)
StartLimitIntervalSec=0
[Service]
-Type=simple
+Type=notify
+KillMode=process
ExecStart=/usr/bin/podman system service