summaryrefslogtreecommitdiff
path: root/libpod/runtime_pod.go
diff options
context:
space:
mode:
authorMatthew Heon <matthew.heon@pm.me>2022-05-16 10:53:11 -0400
committerMatthew Heon <matthew.heon@pm.me>2022-05-16 10:53:11 -0400
commitdc435ecb22fed044ccc348428cbd8160b36977f2 (patch)
treee456929a98c3dee3805073c35f78deba46d7e777 /libpod/runtime_pod.go
parentb94595bdfca2b6f4e69360c806a38b3990ff6f48 (diff)
downloadpodman-dc435ecb22fed044ccc348428cbd8160b36977f2.tar.gz
podman-dc435ecb22fed044ccc348428cbd8160b36977f2.tar.bz2
podman-dc435ecb22fed044ccc348428cbd8160b36977f2.zip
Make errors on removing exec sessions nonfatal
Removing exec sessions is guaranteed to evict them from the DB, but in the case of a zombie process (or similar) it may error and block removal of the container. A subsequent run of `podman rm` would succeed (because the exec sessions have been purged from the DB), which is potentially confusing to users. So let's just continue, instead of erroring out, if removing exec sessions fails. [NO NEW TESTS NEEDED] I wouldn't want to spawn a zombie in our test VMs even if I could. Fixes #14252 Signed-off-by: Matthew Heon <matthew.heon@pm.me>
Diffstat (limited to 'libpod/runtime_pod.go')
0 files changed, 0 insertions, 0 deletions