From 9d40e69de70ecd40a212593f83416e81ea424bc6 Mon Sep 17 00:00:00 2001 From: Erik Hollensbe Date: Tue, 26 Aug 2014 10:59:22 -0700 Subject: [PATCH] Update networking doc with clarified text regarding links usage Docker-DCO-1.1-Signed-off-by: Erik Hollensbe (github: erikh) Upstream-commit: f6a2fc4c3370983043a4284be5d8a09c3ff3bb6e Component: engine --- components/engine/docs/sources/articles/networking.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/components/engine/docs/sources/articles/networking.md b/components/engine/docs/sources/articles/networking.md index 43443e0e18..d61ebd65ba 100644 --- a/components/engine/docs/sources/articles/networking.md +++ b/components/engine/docs/sources/articles/networking.md @@ -150,10 +150,10 @@ Four different options affect container domain name services. `CONTAINER_NAME`. This lets processes inside the new container connect to the hostname `ALIAS` without having to know its IP. The `--link=` option is discussed in more detail below, in the section - [Communication between containers](#between-containers). Docker updates - the ALIAS entry in the /etc/hosts file of the recipient containers - in order to keep the link since Docker may assign a different IP - address to the linked containers on restart. + [Communication between containers](#between-containers). Because + Docker may assign a different IP address to the linked containers + on restart, Docker updates the ALIAS entry in the /etc/hosts file + of the recipient containers. * `--dns=IP_ADDRESS...` — sets the IP addresses added as `server` lines to the container's `/etc/resolv.conf` file. Processes in the