Matthew Heon 3601b96600 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-06-29 09:33:43 -04:00

..

generate

Allow empty host port in --publish flag

2020-06-29 09:33:43 -04:00

config_unsupported.go

Fix the pkg/specgen/SpecGenerator.getSeccompConfig stub

2020-03-20 23:25:15 +01:00

container_validate.go

Fix conflicts between privileged and other flags

2020-06-22 16:08:09 -04:00

namespaces.go

Start testing with cross compilation

2020-05-21 11:58:15 -04:00

pod_validate.go

Fixup issues found by golint

2020-06-10 05:49:41 -04:00

podspecgen.go

pod create: add --infra-conmon-pidfile

2020-06-11 11:01:13 +02:00

specgen.go

Allow empty host port in --publish flag

2020-06-29 09:33:43 -04:00