mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
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 <thomasleveil@gmail.com>
This commit is contained in:
parent
107898a773
commit
906985123a
1 changed files with 2 additions and 2 deletions
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue