Matthew Heon 6b7612062e Correct port range logic for port generation ... The existing logic (Range > 0) always triggered, because range is guaranteed to be at least 1 (a single port has a range of 1, a two port range (e.g. 80-81) has a range of 2, and so on). As such this could cause ports that had a host port assigned to them by the user to randomly assign one instead. Fixes #8650 Fixes #8651 Signed-off-by: Matthew Heon <mheon@redhat.com>		2020-12-08 16:23:14 -05:00
..
generate	Correct port range logic for port generation	2020-12-08 16:23:14 -05:00
config_unsupported.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
container_validate.go	rootless container creation settings	2020-11-05 12:27:48 -06:00
namespaces.go	Support --network=default as if it was private	2020-12-02 18:38:35 -05: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	Add mask and unmask option to --security-opt	2020-12-02 16:07:18 -05:00
volumes.go	Merge branch 'master' into patch-1	2020-11-30 15:58:23 +01:00