summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVincent Demeester <vincent@sbr.pm>2016-04-18 18:16:51 +0200
committerVincent Demeester <vincent@sbr.pm>2016-04-18 18:16:51 +0200
commite764e0215e11da40a1e2148efc9867be362bd2d4 (patch)
treedd235a7108e8fa98b3f799f2303b4c57ba5f7461
parente68765d5e27568d3377f4b5de88b19be4a648a54 (diff)
parentc2e088e13488904a6747809a689eac5d72a4618e (diff)
downloaddocker-e764e0215e11da40a1e2148efc9867be362bd2d4.tar.gz
Merge pull request #22086 from aboch/doc
Clarify container external connectivity in multi-network scenario
-rw-r--r--docs/userguide/networking/dockernetworks.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/userguide/networking/dockernetworks.md b/docs/userguide/networking/dockernetworks.md
index 24cb7ea2a2..dd84872693 100644
--- a/docs/userguide/networking/dockernetworks.md
+++ b/docs/userguide/networking/dockernetworks.md
@@ -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.