You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding support to publish on custom host port ranges
Signed-off-by: Don Kjer <[email protected]>
Changing vendor/src/github.com/docker/libnetwork to match lindenlab/libnetwork custom-host-port-ranges-1.7 branch
Both hostPort and containerPort can be specified as a range of ports.
986
986
When specifying ranges for both, the number of container ports in the range must match the number of host ports in the range. (e.g., `-p 1234-1236:1234-1236/tcp`)
987
+
When specifying a range for hostPort only, the containerPort must not be a range. In this case the container port is published somewhere within the specified hostPort range. (e.g., `-p 1234-1236:1234/tcp`)
987
988
(use 'docker port' to see the actual mapping)
988
989
--link="" : Add link to another container (<name or id>:alias or <name or id>)
0 commit comments