summaryrefslogtreecommitdiff
path: root/libpod
diff options
context:
space:
mode:
authorPaul Holzinger <pholzing@redhat.com>2021-09-01 11:39:42 +0200
committerPaul Holzinger <pholzing@redhat.com>2021-09-01 12:56:38 +0200
commita55f595fe1b84edc20c68c10f264fab82e687364 (patch)
tree6127405a3db421a459781a3beb503f43cf358a95 /libpod
parentbebaef26fdd5d3ae8a29f04d36c437f316fc1bc8 (diff)
downloadpodman-a55f595fe1b84edc20c68c10f264fab82e687364.tar.gz
podman-a55f595fe1b84edc20c68c10f264fab82e687364.tar.bz2
podman-a55f595fe1b84edc20c68c10f264fab82e687364.zip
podman stop always cleanup
When a container is configured for auto removal podman stop should still do cleanup, there is no guarantee the the cleanup process spawned by conmon will be successful. Also a user expects after podman stop that the network/mounts are cleaned up. Therefore podman stop should not return early and instead do the cleanup and ignore errors if the container was already removed. [NO TESTS NEEDED] I don't know how to test this. Fixes #11384 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Diffstat (limited to 'libpod')
0 files changed, 0 insertions, 0 deletions