From 3024604054a588f213b671c7f1ec5eed2c99b78a Mon Sep 17 00:00:00 2001 From: Aditi Rajagopal Date: Fri, 5 Feb 2016 16:45:02 -0600 Subject: [PATCH] Overlay Network needs Unique Hostname Resolves: #19301 Signed-off-by: Aditi Rajagopal --- docs/userguide/networking/get-started-overlay.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/userguide/networking/get-started-overlay.md b/docs/userguide/networking/get-started-overlay.md index 39d7da9169..4854fe6bdb 100644 --- a/docs/userguide/networking/get-started-overlay.md +++ b/docs/userguide/networking/get-started-overlay.md @@ -19,6 +19,7 @@ some pre-existing conditions before you can create one. These conditions are: * Access to a key-value store. Docker supports Consul, Etcd, and ZooKeeper (Distributed store) key-value stores. * A cluster of hosts with connectivity to the key-value store. * A properly configured Engine `daemon` on each host in the cluster. +* Hosts within the cluster must have unique hostnames because the key-value store uses the hostnames to identify cluster members. Though Docker Machine and Docker Swarm are not mandatory to experience Docker multi-host networking, this example uses them to illustrate how they are