From 7efd81cb8dec7a2a173d3abb904d6be05476980a Mon Sep 17 00:00:00 2001 From: Daniel J Walsh Date: Sun, 24 Jul 2022 17:58:36 -0400 Subject: With --rm option remove container if podman run fails Fixes https://github.com/containers/podman/issues/15049 Signed-off-by: Daniel J Walsh Signed-off-by: Matthew Heon --- test/system/030-run.bats | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'test') diff --git a/test/system/030-run.bats b/test/system/030-run.bats index b3e3cef00..39ff3fcd4 100644 --- a/test/system/030-run.bats +++ b/test/system/030-run.bats @@ -853,4 +853,20 @@ EOF run_podman rm $output } +@test "podman run failed --rm " { + port=$(random_free_port) + + # Run two containers with the same port bindings. The second must fail + run_podman run -p $port:80 --rm -d --name c_ok $IMAGE top + run_podman 126 run -p $port:80 -d --name c_fail_no_rm $IMAGE top + run_podman 126 run -p $port:80 --rm -d --name c_fail_with_rm $IMAGE top + # Prior to #15060, the third container would still show up in ps -a + run_podman ps -a --sort names --format '{{.Image}}--{{.Names}}' + is "$output" "$IMAGE--c_fail_no_rm +$IMAGE--c_ok" \ + "podman ps -a shows running & failed containers, but not failed-with-rm" + + run_podman container rm -f -t 0 c_ok c_fail_no_rm +} + # vim: filetype=sh -- cgit v1.2.3-54-g00ecf