From 7580c227348af2a0906a692ad6a44348dc3eefbc Mon Sep 17 00:00:00 2001 From: Daniel J Walsh Date: Mon, 11 Oct 2021 15:02:04 -0400 Subject: Remove a volume with --force if container is running Currently we are not passing the force flag down to the removal of the running container. If the container is running, and we set --force when removing the volume, the container should be stopped. Signed-off-by: Daniel J Walsh --- test/system/160-volumes.bats | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'test/system/160-volumes.bats') diff --git a/test/system/160-volumes.bats b/test/system/160-volumes.bats index 490d635e5..7128f1b65 100644 --- a/test/system/160-volumes.bats +++ b/test/system/160-volumes.bats @@ -97,6 +97,14 @@ Labels.l | $mylabel run_podman volume rm $myvolume } +# Removing volumes with --force +@test "podman volume rm --force" { + run_podman run -d --volume myvol:/myvol $IMAGE top + cid=$output + run_podman 2 volume rm myvol + is "$output" "Error: volume myvol is being used by the following container(s): $cid: volume is being used" "should error since container is running" + run_podman volume rm myvol --force +} # Running scripts (executables) from a volume @test "podman volume: exec/noexec" { -- cgit v1.2.3-54-g00ecf