From 3be52d7f70178edb38bb7cbf4b13f039410dafd1 Mon Sep 17 00:00:00 2001 From: Phil Estes Date: Thu, 11 Sep 2014 15:49:07 -0400 Subject: [PATCH] Match docs to actual port range used in code. Addresses #7985 Docker-DCO-1.1-Signed-off-by: Phil Estes (github: estesp) Upstream-commit: d6f4b2ebb40ac79c3ba21e7196bba3b83124cf16 Component: engine --- components/engine/docs/sources/articles/networking.md | 4 ++-- components/engine/docs/sources/userguide/dockerlinks.md | 4 ++-- components/engine/docs/sources/userguide/usingdocker.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/components/engine/docs/sources/articles/networking.md b/components/engine/docs/sources/articles/networking.md index a47f0d240c..3a990b3aea 100644 --- a/components/engine/docs/sources/articles/networking.md +++ b/components/engine/docs/sources/articles/networking.md @@ -310,13 +310,13 @@ page. There are two approaches. First, you can supply `-P` or `--publish-all=true|false` to `docker run` which is a blanket operation that identifies every port with an `EXPOSE` line in the image's `Dockerfile` and maps it to a host port somewhere in -the range 49000–49900. This tends to be a bit inconvenient, since you +the range 49153–65535. This tends to be a bit inconvenient, since you then have to run other `docker` sub-commands to learn which external port a given service was mapped to. More convenient is the `-p SPEC` or `--publish=SPEC` option which lets you be explicit about exactly which external port on the Docker server — -which can be any port at all, not just those in the 49000–49900 block — +which can be any port at all, not just those in the 49153-65535 block — you want mapped to which port in the container. Either way, you should be able to peek at what Docker has accomplished diff --git a/components/engine/docs/sources/userguide/dockerlinks.md b/components/engine/docs/sources/userguide/dockerlinks.md index 7a5c1514d0..da2f05de99 100644 --- a/components/engine/docs/sources/userguide/dockerlinks.md +++ b/components/engine/docs/sources/userguide/dockerlinks.md @@ -26,8 +26,8 @@ container that ran a Python Flask application: > information on Docker networking [here](/articles/networking/). When that container was created, the `-P` flag was used to automatically map any -network ports inside it to a random high port from the range 49000 -to 49900 on our Docker host. Next, when `docker ps` was run, you saw that +network ports inside it to a random high port from the range 49153 +to 65535 on our Docker host. Next, when `docker ps` was run, you saw that port 5000 in the container was bound to port 49155 on the host. $ sudo docker ps nostalgic_morse diff --git a/components/engine/docs/sources/userguide/usingdocker.md b/components/engine/docs/sources/userguide/usingdocker.md index 40229d4ab6..4810770d13 100644 --- a/components/engine/docs/sources/userguide/usingdocker.md +++ b/components/engine/docs/sources/userguide/usingdocker.md @@ -157,7 +157,7 @@ port) on port 49155. Network port bindings are very configurable in Docker. In our last example the `-P` flag is a shortcut for `-p 5000` that maps port 5000 -inside the container to a high port (from the range 49000 to 49900) on +inside the container to a high port (from the range 49153 to 65535) on the local Docker host. We can also bind Docker containers to specific ports using the `-p` flag, for example: