summaryrefslogtreecommitdiff
path: root/test/system
diff options
context:
space:
mode:
authorPaul Holzinger <pholzing@redhat.com>2022-06-07 14:25:18 +0200
committerMatthew Heon <mheon@redhat.com>2022-06-14 16:12:10 -0400
commit7ca1c267bff22db903a3c6541b51550923340386 (patch)
tree8a2c3a09461f49a6e4eba846686c9d333cb738b9 /test/system
parent3dc9a75473b643ac0bf158e13ecaeb2bb362ed2c (diff)
downloadpodman-7ca1c267bff22db903a3c6541b51550923340386.tar.gz
podman-7ca1c267bff22db903a3c6541b51550923340386.tar.bz2
podman-7ca1c267bff22db903a3c6541b51550923340386.zip
libpod: store network status when userns is used
When a container with a userns is created the network setup is special. Normally the netns is setup before the oci runtime container is created, however with a userns the container is created first and then the network is setup. In the second case we never saved the container state afterwards. Because of it, podman inspect would not show the network info and network teardown will not happen. This worked with local podman because there was a save() call later in the code path which then also saved the network status. But in the podman API code path this save never happened thus all containers started via API had this problem. Fixes #14465 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Diffstat (limited to 'test/system')
-rw-r--r--test/system/500-networking.bats4
1 files changed, 4 insertions, 0 deletions
diff --git a/test/system/500-networking.bats b/test/system/500-networking.bats
index 3db0804d1..92aabae32 100644
--- a/test/system/500-networking.bats
+++ b/test/system/500-networking.bats
@@ -111,6 +111,10 @@ load helpers
$IMAGE nc -l -n -v -p $myport
cid="$output"
+ # check that podman stores the network info correctly when a userns is used (#14465)
+ run_podman container inspect --format "{{.NetworkSettings.SandboxKey}}" $cid
+ assert "$output" =~ ".*/netns/netns-.*" "Netns path should be set"
+
wait_for_output "listening on .*:$myport .*" $cid
# emit random string, and check it