docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #8884 from thomasleveil/userguide-so26652877 

Reword a sentence bringing confusion about docker links
This commit is contained in:
Fred Lifton 2014-10-31 17:09:16 -07:00
parent 92bb497201 906985123a
commit 4d4a7b81bf
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/sources/userguide/dockerlinks.md
View File

@ -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 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. `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 So what does linking the containers actually do? You've learned that a link allows a
source container that can provide information about itself to a recipient container. In 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 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 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 expose any ports externally on the container; you'll note when we started the