Move note on top of Nodes config to avoid confusion

Signed-off-by: Alexandre Beslic <alexandre.beslic@gmail.com>
This commit is contained in:
Alexandre Beslic 2015-03-25 09:57:11 -07:00
parent 904c720ea5
commit ca245c6ad3
1 changed files with 5 additions and 5 deletions

View File

@ -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 Docker daemon, and will then monitor it, updating the discovery backend to its
status. 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: The following example uses the Docker Hub based `token` discovery service:
```bash ```bash
@ -70,11 +75,6 @@ $ docker run --rm swarm list token://<cluster_id>
<node_ip:2375> <node_ip:2375>
``` ```
> **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 ## TLS
Swarm supports TLS authentication between the CLI and Swarm but also between Swarm supports TLS authentication between the CLI and Swarm but also between