Sascha Grunert 49424fc02a Fix host to container port mapping for simple ranges ... 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>		2020-10-19 11:19:12 +02:00
..
generate	Fix host to container port mapping for simple ranges	2020-10-19 11:19:12 +02:00
config_unsupported.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
container_validate.go	error when adding container to pod with network information	2020-08-21 09:21:15 -05:00
namespaces.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
pod_validate.go	Add support for slirp network for pods	2020-09-25 21:34:23 -04:00
podspecgen.go	Add support for slirp network for pods	2020-09-25 21:34:23 -04:00
specgen.go	Support max_size logoptions	2020-10-05 17:51:45 -04:00