podman: podman rm: fails, and leaves everything hosed

Another hard-to-isolate flake. I’m not convinced that it’s truly podman-remote-only, because I’ve actually seen this one on my laptop. Two symptoms (possibly unrelated):

# podman-remote --url unix:/tmp/podman_tmp_loGI rm -t 0 -f cpcontainer
Error: cannot remove container 5d183a4ab677c5b65a78ebf87720153aee486145b24631f08edb7e20671498b7 as it could not be stopped: error sending SIGKILL to container 5d183a4ab677c5b65a78ebf87720153aee486145b24631f08edb7e20671498b7: %!w(<nil>)
[ rc=125 (** EXPECTED 0 **) ]

and

# podman-remote --url unix:/tmp/podman_tmp_fYnD pod rm -f -t 0 -a
Error: error freeing lock for container 38ecd608db0c5616563d5b268e85fea2fbada7a9b7d57eabf705c4f8f92aca92: no such file or directory
[ rc=125 (** EXPECTED 0 **) ]

With the second one, once it happens, the entire system becomes completely unusable.

Here’s an example of the cannot-remove one

Here’s an example of the error-freeing one

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 42 (8 by maintainers)

Commits related to this issue

container kill: handle stopped/exited container The container lock is released before stopping/killing which implies certain race conditions with, for instance, the cleanup process changing the conta... — committed to vrothberg/libpod by vrothberg a year ago

Most upvoted comments

@Johnpc123 to help you out, i was able to remove the pod that i borked like you did by removing it through the cockpit-podman web interface. it threw that error at me but was able to remove it completely nonetheless, while podman pod rm gitea -f couldn’t

maisatanel on Dec 5, 2022