diff options
| author | Daniel J Walsh <dwalsh@redhat.com> | 2021-05-21 08:00:47 -0400 |
|---|---|---|
| committer | Matthew Heon <mheon@redhat.com> | 2021-05-25 15:17:35 -0400 |
| commit | ac8b7ddd8dc2b3d4ac2da6b4ddd08b900eb02353 (patch) | |
| tree | b716919ca2d1f47d57dca907524c9c36979af82b /docs/source/markdown/links/podman-container-restart.1 | |
| parent | 18e917cdc361dc7f1badbce89b69e80a522062fe (diff) | |
| download | podman-ac8b7ddd8dc2b3d4ac2da6b4ddd08b900eb02353.tar.gz podman-ac8b7ddd8dc2b3d4ac2da6b4ddd08b900eb02353.tar.bz2 podman-ac8b7ddd8dc2b3d4ac2da6b4ddd08b900eb02353.zip | |
Drop container does not exist on removal to debugf
We have race conditions where a container can be removed
by two different processes when running podman --remove rm.
It can be cleaned up in the API or by the conmon executing
podman container cleanup.
When we fail to remove a container that does not exists we should
not be printing errors or warnings, we should just debug the fact.
[NO TESTS NEEDED] Since this is a race condition it is difficult to
test.
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'docs/source/markdown/links/podman-container-restart.1')
0 files changed, 0 insertions, 0 deletions