diff options
| author | Matthew Heon <mheon@redhat.com> | 2020-11-03 10:01:21 -0500 |
|---|---|---|
| committer | Matthew Heon <mheon@redhat.com> | 2020-11-04 13:42:58 -0500 |
| commit | a4da384b559796ecbf49746e655876138d494864 (patch) | |
| tree | 50e87b3ea83db2dc4dc8acd9484867ed33fafbd9 /test/system | |
| parent | 4d87306fbe06674b16f188fea187282f29c0dc58 (diff) | |
| download | podman-a4da384b559796ecbf49746e655876138d494864.tar.gz podman-a4da384b559796ecbf49746e655876138d494864.tar.bz2 podman-a4da384b559796ecbf49746e655876138d494864.zip | |
Ensure that --net=host/pod/container/none warn with -p
Setting port mappings only works when CNI is configuring our
network (or slirp4netns, in the rootless case). This is not the
case with `--net=host`, `--net=container:`, and joining the
network namespace of the pod we are part of. Instead of allowing
users to do these things and then be confused why they do
nothing, let's match Docker and return a warning that your port
mappings will do nothing.
Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'test/system')
| -rw-r--r-- | test/system/030-run.bats | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/test/system/030-run.bats b/test/system/030-run.bats index 6b6964c63..b64e80f05 100644 --- a/test/system/030-run.bats +++ b/test/system/030-run.bats @@ -522,4 +522,9 @@ json-file | f run_podman untag $IMAGE $newtag $newtag2 } +@test "podman run with --net=host and --port prints warning" { + run_podman run -d --rm -p 8080 --net=host $IMAGE ls > /dev/null + is "$output" ".*Port mappings have been discarded as one of the Host, Container, Pod, and None network modes are in use" +} + # vim: filetype=sh |