Matthew Heon a4da384b55 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>		2020-11-04 13:42:58 -05:00
..
config_linux.go	spec: open fuse with --device .*/fuse	2020-10-02 10:12:58 +02:00
config_linux_cgo.go	Remove excessive error wrapping	2020-10-05 15:30:37 -07:00
config_linux_nocgo.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
container.go	Ensure that --net=host/pod/container/none warn with -p	2020-11-04 13:42:58 -05:00
container_create.go	container create: record correct image name	2020-10-21 16:51:09 +02:00
namespaces.go	Ensure that hostname is added to hosts with net=host	2020-10-20 10:31:15 -04:00
oci.go	refactor api compatibility container creation to specgen	2020-10-20 12:06:59 -05:00
pod_create.go	Add support for slirp network for pods	2020-09-25 21:34:23 -04:00
ports.go	Fix host to container port mapping for simple ranges	2020-10-19 11:19:12 +02:00
security.go	capabilities: always set ambient and inheritable	2020-09-30 15:14:07 +02:00
storage.go	Fix incorrect parsing of create/run --volumes-from	2020-09-20 22:49:09 +02:00
validate.go	podman: add option --cgroup-conf	2020-08-21 19:06:05 +02:00