summaryrefslogtreecommitdiff
path: root/libpod/runtime_renumber.go
diff options
context:
space:
mode:
authorPaul Holzinger <paul.holzinger@web.de>2020-08-20 11:07:36 +0200
committerMatthew Heon <matthew.heon@pm.me>2020-08-20 14:59:21 -0400
commit7fc3c25410bd5ee053473ffd5df2209f41840ec0 (patch)
tree51454c02b2bc2c6680833e7c52f38f956dbc46ad /libpod/runtime_renumber.go
parentf12f2456afe50ebf4622945bebd71e7134b9dd9c (diff)
downloadpodman-7fc3c25410bd5ee053473ffd5df2209f41840ec0.tar.gz
podman-7fc3c25410bd5ee053473ffd5df2209f41840ec0.tar.bz2
podman-7fc3c25410bd5ee053473ffd5df2209f41840ec0.zip
fix pod creation with "new:" syntax followup + allow hostname
Fixes: 4c75fe3f70ed ("fix pod creation with "new:" syntax") Commit 4c75fe3f70ed passes all net options to the pod but forgot to unset the options for the container creation. This leads to erros when using flags like `--ip` since we tried setting the ip on the pod and container which obviously fails. I didn't notice the bug because we don't throw an error when specifing port bindings on a container which joins the pods network namespace. (#7373) Also allow the use of `--hostname` and pass that option to the pod and unset it for the container. The container has to use the pods hostname anyway. This would error otherwise. Added tests to prevent regression. Signed-off-by: Paul Holzinger <paul.holzinger@web.de>
Diffstat (limited to 'libpod/runtime_renumber.go')
0 files changed, 0 insertions, 0 deletions