Browse Source

Clarify container external connectivity in multi-network scenario

Signed-off-by: Alessandro Boch <aboch@docker.com>
(cherry picked from commit c2e088e13488904a6747809a689eac5d72a4618e)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Alessandro Boch 9 years ago
parent
commit
b9f11557af
1 changed files with 3 additions and 1 deletions
  1. 3 1
      docs/userguide/networking/dockernetworks.md

+ 3 - 1
docs/userguide/networking/dockernetworks.md

@@ -293,7 +293,9 @@ specifications.
 You can create multiple networks. You can add containers to more than one
 You can create multiple networks. You can add containers to more than one
 network. Containers can only communicate within networks but not across
 network. Containers can only communicate within networks but not across
 networks. A container attached to two networks can communicate with member
 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
 The next few sections describe each of Docker's built-in network drivers in
 greater detail.
 greater detail.