From e34558a69d90bf70f030549da23c470a715019cf Mon Sep 17 00:00:00 2001 From: Dan Cotora Date: Mon, 22 Sep 2014 08:36:20 +0300 Subject: [PATCH] Doc update to clarify random port mapping on docker run -P Signed-off-by: Dan Cotora Upstream-commit: d6d5dcd55ad77010b7b7042847bb34215f701a76 Component: cli --- components/cli/docs/sources/reference/run.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/components/cli/docs/sources/reference/run.md b/components/cli/docs/sources/reference/run.md index 81afb96cd1..5bdaa256d6 100644 --- a/components/cli/docs/sources/reference/run.md +++ b/components/cli/docs/sources/reference/run.md @@ -381,8 +381,9 @@ with `-P` or `-p,` or start the client container with `--link`. If the operator uses `-P` or `-p` then Docker will make the exposed port accessible on the host and the ports will be available to any client -that can reach the host. To find the map between the host ports and the -exposed ports, use `docker port`) +that can reach the host. When using `-P`, Docker will bind the exposed +ports to a random port on the host between 49153 and 65535. To find the +mapping between the host ports and the exposed ports, use `docker port`. If the operator uses `--link` when starting the new client container, then the client container can access the exposed port via a private