From 74a010ee39a78a1d9523035b2c7ab4045bc35776 Mon Sep 17 00:00:00 2001 From: Alessandro Boch Date: Fri, 15 Apr 2016 17:15:18 -0700 Subject: [PATCH] Clarify container external connectivity in multi-network scenario Signed-off-by: Alessandro Boch Upstream-commit: c2e088e13488904a6747809a689eac5d72a4618e Component: engine --- components/engine/docs/userguide/networking/dockernetworks.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/components/engine/docs/userguide/networking/dockernetworks.md b/components/engine/docs/userguide/networking/dockernetworks.md index 1848e7a7a9..5adb1b3c05 100644 --- a/components/engine/docs/userguide/networking/dockernetworks.md +++ b/components/engine/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.