mirror of
https://github.com/containers/podman.git
synced 2025-05-17 23:26:08 +08:00
9e38b455e4
If volume ls was called while another volume was removed at the right time it could have failed with "no such volume" as we did not ignore such error during listing. As we list things and this no longer exists the correct thing is to ignore the error and continue like we do with containers, pods, etc... This was pretty easy to reproduce with these two commands running in different terminals: while :; do bin/podman volume create test && bin/podman volume rm test || break; done while :; do bin/podman volume ls || break ; done I have a slight feeling that this might solve #23913 but I am not to sure there so I am not adding a Fixes here. Signed-off-by: Paul Holzinger <pholzing@redhat.com> (cherry picked from commit 9a0c0b2eef962bdb63372ed0ccd2bb6b1e5de3b8) Signed-off-by: Paul Holzinger <pholzing@redhat.com>