mirror of https://github.com/containers/podman.git
a619c03eff
Previously, we didn't bother including exposed ports in the container config when creating a container with --net=host. Per Docker this isn't really correct; host-net containers are still considered to have exposed ports, even though that specific container can be guaranteed to never use them. We could just fix this for host container, but we might as well make it generic. This patch unconditionally adds exposed ports to the container config - it was previously conditional on a network namespace being configured. The behavior of `podman inspect` with exposed ports when using `--net=container:` has also been corrected. Previously, we used exposed ports from the container sharing its network namespace, which was not correct. Now, we use regular port bindings from the namespace container, but exposed ports from our own container. Fixes https://issues.redhat.com/browse/RHEL-60382 Signed-off-by: Matt Heon <mheon@redhat.com> |
||
|---|---|---|
| .. | ||
| kube | ||
| config_common.go | ||
| config_common_test.go | ||
| config_freebsd.go | ||
| config_linux.go | ||
| config_linux_seccomp.go | ||
| config_linux_test.go | ||
| container.go | ||
| container_create.go | ||
| namespaces.go | ||
| namespaces_freebsd.go | ||
| namespaces_linux.go | ||
| oci.go | ||
| oci_freebsd.go | ||
| oci_linux.go | ||
| pause_image.go | ||
| pod_create.go | ||
| pod_create_test.go | ||
| ports.go | ||
| ports_bench_test.go | ||
| ports_test.go | ||
| security_freebsd.go | ||
| security_linux.go | ||
| storage.go | ||
| storage_freebsd.go | ||
| storage_linux.go | ||
| validate_freebsd.go | ||
| validate_linux.go | ||