Matthew Heon 1c02d5ab89 Allow empty host port in --publish flag ... I didn't believe that this was actually legal, but it looks like it is. And, unlike our previous understanding (host port being empty means just use container port), empty host port actually carries the same meaning as `--expose` + `--publish-all` (that is, assign a random host port to the given container port). This requires a significant rework of our port handling code to handle this new case. I don't foresee this being commonly used, so I optimized having a fixed port number as fast path, which this random assignment code running after the main port handling code only if necessary. Fixes #6806 Signed-off-by: Matthew Heon <matthew.heon@pm.me>		2020-07-06 13:37:27 -04:00
..
create.go	move go module to v2	2020-07-06 15:52:17 +02:00
create_opts.go	move go module to v2	2020-07-06 15:52:17 +02:00
createparse.go	move go module to v2	2020-07-06 15:52:17 +02:00
default.go	move go module to v2	2020-07-06 15:52:17 +02:00
netflags.go	move go module to v2	2020-07-06 15:52:17 +02:00
ports.go	V2 enable ps tests	2020-04-29 15:51:37 -07:00
specgen.go	move go module to v2	2020-07-06 15:52:17 +02:00
util.go	Allow empty host port in --publish flag	2020-07-06 13:37:27 -04:00
volumes.go	move go module to v2	2020-07-06 15:52:17 +02:00