From f1bc02e91f79b4a54f47e0ad4abfd3d48b698ec4 Mon Sep 17 00:00:00 2001 From: Mehul Kar Date: Thu, 29 Jan 2015 09:09:44 -0800 Subject: [PATCH] Improve explanation of port mapping from containers Signed-off-by: Mehul Kar --- docs/sources/userguide/usingdocker.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/sources/userguide/usingdocker.md b/docs/sources/userguide/usingdocker.md index 865f446bd0..12a6b6fb2f 100644 --- a/docs/sources/userguide/usingdocker.md +++ b/docs/sources/userguide/usingdocker.md @@ -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 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 -Python applications: both bound to port 5000 inside your container. -Without Docker's port mapping you could only access one at a time. +Python applications: both bound to port 5000 inside their own containers. +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 see the application.