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