From 0a4b39b6a4e9faeea5d8c679e7b03e317a7b02f9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Roland=20Hu=C3=9F?= Date: Wed, 23 Jul 2014 10:23:14 +0200 Subject: [PATCH] Fixed parent-child relationship description "db" is the parent image, and "web" links to it as the child image. There was a typo in the document which reversed the relation. --- 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 d7a2abff9c..c1d8c14681 100644 --- a/docs/sources/userguide/dockerlinks.md +++ b/docs/sources/userguide/dockerlinks.md @@ -162,8 +162,8 @@ containers also shows `web/db` in the `NAMES` column. This tells us that the `web` container is linked to the `db` container in a parent/child relationship. So what does linking the containers do? Well we've discovered the link creates -a parent-child relationship between the two containers. The parent container, -here `web`, can access information on the child container `db`. To do this +a parent-child relationship between the two containers. The child container, +here `web`, can access information on the parent container `db`. To do this Docker creates a secure tunnel between the containers without the need to expose any ports externally on the container. You'll note when we started the `db` container we did not use either of the `-P` or `-p` flags. As we're