From ca245c6ad3e1e44102134b9d3366213b53be5099 Mon Sep 17 00:00:00 2001 From: Alexandre Beslic Date: Wed, 25 Mar 2015 09:57:11 -0700 Subject: [PATCH] Move note on top of Nodes config to avoid confusion Signed-off-by: Alexandre Beslic --- docs/index.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/index.md b/docs/index.md index 5189d834cb..88d7a5b3ca 100644 --- a/docs/index.md +++ b/docs/index.md @@ -43,6 +43,11 @@ Each swarm node will run a swarm node agent which will register the referenced Docker daemon, and will then monitor it, updating the discovery backend to its status. +> **Note**: In order for the Swarm manager to be able to communicate with the node +agent on each node, they must listen to a common network interface. This can be +achieved by starting docker with the `-H` flag (e.g. `docker -H tcp://0.0.0.0:2375 -d` +on each swarm node). + The following example uses the Docker Hub based `token` discovery service: ```bash @@ -70,11 +75,6 @@ $ docker run --rm swarm list token:// ``` -> **Note**: In order for the Swarm manager to be able to communicate with the node agent on -each node, they must listen to a common network interface. This can be achieved -by starting with the `-H` flag (e.g. `-H tcp://0.0.0.0:2375`). - - ## TLS Swarm supports TLS authentication between the CLI and Swarm but also between