0ct0pu5/moby
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify container external connectivity in multi-network scenario

Browse source 
Signed-off-by: Alessandro Boch <aboch@docker.com>
(cherry picked from commit c2e088e134)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Alessandro Boch 2016-04-15 17:15:18 -07:00 • committed by Sebastiaan van Stijn
parent ce9bc253f6
commit b9f11557af
No known key found for this signature in database
GPG key ID: 76698F39D527CE8C
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/userguide/networking/dockernetworks.md
View file

@ -293,7 +293,9 @@ specifications.
You can create multiple networks. You can add containers to more than one
network. Containers can only communicate within networks but not across
networks. A container attached to two networks can communicate with member
containers in either network.
containers in either network. When a container is connected to multiple
networks, its external connectivity is provided via the first non-internal
network, in lexical order.
The next few sections describe each of Docker's built-in network drivers in
greater detail.