summaryrefslogtreecommitdiff
path: root/libpod/container_log_unsupported.go
diff options
context:
space:
mode:
authorValentin Rothberg <rothberg@redhat.com>2021-02-23 13:02:35 +0100
committerValentin Rothberg <rothberg@redhat.com>2021-02-23 13:02:35 +0100
commite5ac28f3b968661e5c2603880a5c4576d590f3dd (patch)
tree378d34ca1cb862ea65deff2292085198a39770da /libpod/container_log_unsupported.go
parent96fc9d983e0fc5bae48c3cec3acce86cdb6e1059 (diff)
downloadpodman-e5ac28f3b968661e5c2603880a5c4576d590f3dd.tar.gz
podman-e5ac28f3b968661e5c2603880a5c4576d590f3dd.tar.bz2
podman-e5ac28f3b968661e5c2603880a5c4576d590f3dd.zip
container removal: handle already removed containers
Since commit d54478d8eaec, a container's lock is released before attempting to stop it via the OCI runtime. This opened the window for various kinds of race conditions. One of them led to #9479 where the removal+cleanup sequences of a `run --rm` session overlapped with `rm -af`. Make both execution paths more robust by handling the case of an already removed container. Fixes: #9479 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'libpod/container_log_unsupported.go')
0 files changed, 0 insertions, 0 deletions