summaryrefslogtreecommitdiff
path: root/pkg/annotations/annotations.go
diff options
context:
space:
mode:
authorValentin Rothberg <rothberg@redhat.com>2020-06-17 14:48:19 +0200
committerValentin Rothberg <rothberg@redhat.com>2020-06-17 18:52:44 +0200
commite5c3432944245a740ed443803c654dcc9c3757f0 (patch)
treed95dd4508d1e3f847cda3787586062acecd165e1 /pkg/annotations/annotations.go
parentf293606480669acea375c53de1e2c81044313c05 (diff)
downloadpodman-e5c3432944245a740ed443803c654dcc9c3757f0.tar.gz
podman-e5c3432944245a740ed443803c654dcc9c3757f0.tar.bz2
podman-e5c3432944245a740ed443803c654dcc9c3757f0.zip
generate systemd: `ExecStopPost` for all units
Add an `ExecStopPost` run even for units generated without `--new`. Although it may seem redundant to run `container/pod stop` twice at first glance, we really need the post run. If the main PID (i.e., conmon) is killed, systemd will not execute `ExecStop` but only the post one. We made this obeservation in a customer issue and could reproduce the behavior consistently. Hence, the post run is needed to properly clean up when conmon is killed and it's pretty much a NOP in all other cases. Credits to Ulrich Obergfell for throrough and detailed analyses, which ultimately lead to this fix. Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'pkg/annotations/annotations.go')
0 files changed, 0 insertions, 0 deletions