From 906985123aa6b7874c3c0e21f0fb5603928ff6dd Mon Sep 17 00:00:00 2001 From: Thomas LEVEIL Date: Fri, 31 Oct 2014 13:00:59 +0000 Subject: [PATCH] Reword a sentence bringing confusion about docker links As [discovered][1] doing user support, the sentence `You've learned that a link creates a source container that can provide information about itself to a recipient container` brings confusion. [1]: http://stackoverflow.com/questions/26652877/how-to-avoid-redundant-container-linking-in-docker-when-propagating-ip-addresses/26654203?noredirect=1#comment41945048_26654203 Signed-off-by: Thomas LEVEIL --- docs/sources/userguide/dockerlinks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sources/userguide/dockerlinks.md b/docs/sources/userguide/dockerlinks.md index 631f4bdea5..fa665b7266 100644 --- a/docs/sources/userguide/dockerlinks.md +++ b/docs/sources/userguide/dockerlinks.md @@ -159,8 +159,8 @@ Next, inspect your linked containers with `docker inspect`: You can see that the `web` container is now linked to the `db` container `web/db`. Which allows it to access information about the `db` container. -So what does linking the containers actually do? You've learned that a link creates a -source container that can provide information about itself to a recipient container. In +So what does linking the containers actually do? You've learned that a link allows a +source container to provide information about itself to a recipient container. In our example, the recipient, `web`, can access information about the source `db`. To do this, Docker creates a secure tunnel between the containers that doesn't need to expose any ports externally on the container; you'll note when we started the