diff options
author | Matthew Heon <mheon@redhat.com> | 2021-08-18 14:19:11 -0400 |
---|---|---|
committer | Matthew Heon <mheon@redhat.com> | 2021-08-18 14:19:11 -0400 |
commit | 592fae4225619755bdcc9f26416eab1c450f9811 (patch) | |
tree | 5b8290d58efc69e174e74b249391f53edf218d9a /contrib/systemd/system/podman.socket | |
parent | a3d8b48fd56a722642f7cbcad52b2fa88f12b656 (diff) | |
download | podman-592fae4225619755bdcc9f26416eab1c450f9811.tar.gz podman-592fae4225619755bdcc9f26416eab1c450f9811.tar.bz2 podman-592fae4225619755bdcc9f26416eab1c450f9811.zip |
Volumes: Only remove from DB if plugin removal succeeds
Originally, Podman would unconditionally remove volumes from the
DB, even if they failed to be removed from the volume plugin;
this was a safety measure to ensure that `volume rm` can always
remove a volume from the database, even if the plugin is
misbehaving.
However, this is a significant deivation from Docker, which
refuses to remove if the plugin errors. These errors can be
legitimate configuration issues which the user should address
before the volume is removed, so Podman should also use this
behaviour.
Fixes #11214
Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'contrib/systemd/system/podman.socket')
0 files changed, 0 insertions, 0 deletions