mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-09-03 06:07:51 +00:00
This fixes the issue that a simple port range should map to a random port range from the host to the container, if no host port range is specified. For example this fails without applying the patch: ``` > podman run -it -p 6000-6066 alpine Error: cannot listen on the TCP port: listen tcp4 :53: bind: address already in use ``` The issue is that only the first port is randomly chosen and all following in the range start by 0 and increment. This is now fixed by tracking the ranges and then incrementing the random port if necessary. Signed-off-by: Sascha Grunert <sgrunert@suse.com> |
||
|---|---|---|
| .. | ||
| config_linux.go | ||
| config_linux_cgo.go | ||
| config_linux_nocgo.go | ||
| container.go | ||
| container_create.go | ||
| namespaces.go | ||
| oci.go | ||
| pod_create.go | ||
| ports.go | ||
| security.go | ||
| storage.go | ||
| validate.go | ||