From 49acf8c52266667ff1c17515a40d10f02a95837b Mon Sep 17 00:00:00 2001 From: Don Kjer Date: Fri, 1 May 2015 19:35:26 +0000 Subject: [PATCH] Adding support to publish on custom host port ranges Signed-off-by: Don Kjer Changing vendor/src/github.com/docker/libnetwork to match lindenlab/libnetwork custom-host-port-ranges-1.7 branch --- docs/reference/run.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/reference/run.md b/docs/reference/run.md index 23852b5a21..913270e120 100644 --- a/docs/reference/run.md +++ b/docs/reference/run.md @@ -984,6 +984,7 @@ or override the Dockerfile's exposed defaults: format: ip:hostPort:containerPort | ip::containerPort | hostPort:containerPort | containerPort Both hostPort and containerPort can be specified as a range of ports. 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`) + 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`) (use 'docker port' to see the actual mapping) --link="" : Add link to another container (:alias or )