diff options
| author | Valentin Rothberg <rothberg@redhat.com> | 2020-08-13 12:53:28 +0200 |
|---|---|---|
| committer | Valentin Rothberg <rothberg@redhat.com> | 2020-08-13 17:53:59 +0200 |
| commit | 0f4e2be0733ac9806b281627b6c8466e61611435 (patch) | |
| tree | 34a71f4eefaaaa2bd90552fbc2c06e0a940a00a9 /contrib/systemd/system | |
| parent | d777a7bd5c920ce3cf06c4eba25068747dbc6b8f (diff) | |
| download | podman-0f4e2be0733ac9806b281627b6c8466e61611435.tar.gz podman-0f4e2be0733ac9806b281627b6c8466e61611435.tar.bz2 podman-0f4e2be0733ac9806b281627b6c8466e61611435.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/systemd/system')
| -rw-r--r-- | contrib/systemd/system/podman.service | 3 |
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 |