docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Improve explanation of port mapping from containers 

Signed-off-by: Mehul Kar <mehul.kar@gmail.com>
This commit is contained in:
Mehul Kar 2015-01-29 09:09:44 -08:00
parent b505db5e3c
commit f1bc02e91f
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/sources/userguide/usingdocker.md
View File

@ -167,8 +167,9 @@ host. You might be asking about now: why wouldn't we just want to always
use 1:1 port mappings in Docker containers rather than mapping to high use 1:1 port mappings in Docker containers rather than mapping to high
ports? Well 1:1 mappings have the constraint of only being able to map ports? Well 1:1 mappings have the constraint of only being able to map
one of each port on your local host. Let's say you want to test two one of each port on your local host. Let's say you want to test two
Python applications: both bound to port 5000 inside your container. Python applications: both bound to port 5000 inside their own containers.
Without Docker's port mapping you could only access one at a time. Without Docker's port mapping you could only access one at a time on the
Docker host.
So let's now browse to port 49155 in a web browser to So let's now browse to port 49155 in a web browser to
see the application. see the application.