Matthew Heon da752a7ed3 Binding the same container port to >1 host port is OK ... The initial version of the new port code mistakenly restricted this, so un-restrict it. We still need to maintain the map of container ports, unfortunately (need to verify if the port in question is a duplicate, for example). Fixes #7062 Signed-off-by: Matthew Heon <matthew.heon@pm.me>		2020-07-31 11:41:05 -04:00
..
config_linux.go	Mask out /sys/dev to prevent information leak from the host	2020-07-22 14:35:30 -04:00
config_linux_cgo.go	move go module to v2	2020-07-06 15:52:17 +02:00
config_linux_nocgo.go	move go module to v2	2020-07-06 15:52:17 +02:00
container.go	Pids-limit should only be set if the user set it	2020-07-06 14:14:48 -04:00
container_create.go	Fix container and pod create commands for remote create	2020-07-22 14:39:41 -04:00
namespaces.go	move go module to v2	2020-07-06 15:52:17 +02:00
oci.go	Fix handling of entrypoint	2020-07-22 14:53:26 -04:00
pod_create.go	Fix container and pod create commands for remote create	2020-07-22 14:39:41 -04:00
ports.go	Binding the same container port to >1 host port is OK	2020-07-31 11:41:05 -04:00
security.go	Support default profile for apparmor	2020-07-22 13:14:15 -04:00
storage.go	move go module to v2	2020-07-06 15:52:17 +02:00
validate.go	move go module to v2	2020-07-06 15:52:17 +02:00