Browse code
Update networkingcontainers.md
updated line on how to exit the container after the ping test - in my environment (Ubuntu 14.04.1, bash) ctrl-c does not work to exit the shell, and `exit` must be used instead.
Signed-off-by: Troy Denton <Troy.Denton@younessleeptechnologies.com>
Troy Denton authored on 2015/12/10 04:07:31Showing 1 changed files
| ... | ... |
@@ -221,7 +221,7 @@ Now, open a shell to your running `db` container: |
| 221 | 221 |
--- 172.17.0.2 ping statistics --- |
| 222 | 222 |
44 packets transmitted, 0 received, 100% packet loss, time 43185ms |
| 223 | 223 |
|
| 224 |
-After a bit, use CTRL-C to end the `ping` and you'll find the ping failed. That is because the two container are running on different networks. You can fix that. Then, use CTRL-C to exit the container. |
|
| 224 |
+After a bit, use CTRL-C to end the `ping` and you'll find the ping failed. That is because the two container are running on different networks. You can fix that - use the `exit` command to exit the container. |
|
| 225 | 225 |
|
| 226 | 226 |
Docker networking allows you to attach a container to as many networks as you like. You can also attach an already running container. Go ahead and attach your running `web` app to the `my-bridge-network`. |
| 227 | 227 |
|