kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity

Merge pull request #24610 from sfsmithcha/rc4_tutorial_check

Browse source 
update create swarm and add nodes to use the auto-generated join command
This commit is contained in:
Sebastiaan van Stijn 2016-07-15 19:09:36 +02:00 • committed by GitHub
commit 9a9fc01af8
2 changed files with 55 additions and 40 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

41
docs/swarm/swarm-tutorial/add-nodes.md
View file

@ -19,34 +19,41 @@ to add worker nodes.
1. Open a terminal and ssh into the machine where you want to run a worker node. 1. Open a terminal and ssh into the machine where you want to run a worker node.
This tutorial uses the name `worker1`. This tutorial uses the name `worker1`.
2. Run the following command to create a worker node joined to 2. Run the command produced by the `docker swarm init` output from the
the existing swarm: [Create a swarm](create-swarm.md) tutorial step to create a worker node joined to the existing swarm:
```bash
$ docker swarm join --secret 4ao565v9jsuogtq5t8s379ulb \
--ca-hash sha256:07ce22bd1a7619f2adc0d63bd110479a170e7c4e69df05b67a1aa2705c88ef09 \
192.168.99.100:2377
``` ```
If you don't have the command available, you can run the following command:
```bash
docker swarm join --secret <SECRET> <MANAGER-IP>:<PORT> docker swarm join --secret <SECRET> <MANAGER-IP>:<PORT>
``` ```
Replace `<SECRET>` with the secret that was printed by `docker swarm init` in the Replace `<SECRET>` with the secret that was printed by `docker swarm init`
previous step. Replace `<MANAGER-IP>` with the address of the manager node in the previous step. Replace `<MANAGER-IP>` with the address of the manager
and `<PORT>` with the port where the manager listens. node and `<PORT>` with the port where the manager listens.
In the tutorial, the following command joins `worker1` to the swarm on `manager1`: The command generated from `docker swarm init` includes the `--ca-hash` to
securely identify the manager node according to its root CA. For the
``` tutorial, it is OK to join without it.
$ docker swarm join --secret 4ao565v9jsuogtq5t8s379ulb 192.168.99.100:2377
This node joined a Swarm as a worker.
```
3. Open a terminal and ssh into the machine where you want to run a second 3. Open a terminal and ssh into the machine where you want to run a second
worker node. This tutorial uses the name `worker2`. worker node. This tutorial uses the name `worker2`.
4. Run `docker swarm join --secret <SECRET> <MANAGER-IP>:<PORT>` to create a worker node joined to 4. Run the command produced by the `docker swarm init` output from the
the existing Swarm. [Create a swarm](create-swarm.md) tutorial step to create a second worker node
joined to the existing swarm:
Replace `<SECRET>` with the secret that was printed by `docker swarm init` in the ```bash
previous step. Replace `<MANAGER-IP>` with the address of the manager node $ docker swarm join --secret 4ao565v9jsuogtq5t8s379ulb \
and `<PORT>` with the port where the manager listens. --ca-hash sha256:07ce22bd1a7619f2adc0d63bd110479a170e7c4e69df05b67a1aa2705c88ef09 \
192.168.99.100:2377
```
5. Open a terminal and ssh into the machine where the manager node runs and run 5. Open a terminal and ssh into the machine where the manager node runs and run
the `docker node ls` command to see the worker nodes: the `docker node ls` command to see the worker nodes:

22
docs/swarm/swarm-tutorial/create-swarm.md
View file

@ -22,18 +22,20 @@ node. For example, the tutorial uses a machine named `manager1`.
2. Run the following command to create a new swarm: 2. Run the following command to create a new swarm:
``` ```bash
docker swarm init --listen-addr <MANAGER-IP>:<PORT> docker swarm init --listen-addr <MANAGER-IP>:<PORT>
``` ```
In the tutorial, the following command creates a swarm on the `manager1` machine: In the tutorial, the following command creates a swarm on the `manager1`
machine:
``` ```bash
$ docker swarm init --listen-addr 192.168.99.100:2377 $ docker swarm init --listen-addr 192.168.99.100:2377
No --secret provided. Generated random secret: No --secret provided. Generated random secret:
4ao565v9jsuogtq5t8s379ulb 4ao565v9jsuogtq5t8s379ulb
Swarm initialized: current node (dxn1zf6l61qsb1josjja83ngz) is now a manager. Swarm initialized: current node (dxn1zf6l61qsb1josjja83ngz) is now a
manager.
To add a worker to this swarm, run the following command: To add a worker to this swarm, run the following command:
docker swarm join --secret 4ao565v9jsuogtq5t8s379ulb \ docker swarm join --secret 4ao565v9jsuogtq5t8s379ulb \
@ -45,9 +47,15 @@ node. For example, the tutorial uses a machine named `manager1`.
`2377`. The other nodes in the swarm must be able to access the manager at `2377`. The other nodes in the swarm must be able to access the manager at
the IP address. the IP address.
The `--ca-hash` flag provides the identity of the root CA for the manager
node.
2. Save the output of `docker swarm init` that includes the command to join
worker nodes to the swarm.
3. Run `docker info` to view the current state of the swarm: 3. Run `docker info` to view the current state of the swarm:
``` ```bash
$ docker info $ docker info
Containers: 2 Containers: 2
@ -66,7 +74,7 @@ node. For example, the tutorial uses a machine named `manager1`.
4. Run the `docker node ls` command to view information about nodes: 4. Run the `docker node ls` command to view information about nodes:
``` ```bash
$ docker node ls $ docker node ls
ID HOSTNAME MEMBERSHIP STATUS AVAILABILITY MANAGER STATUS LEADER ID HOSTNAME MEMBERSHIP STATUS AVAILABILITY MANAGER STATUS LEADER
@ -74,7 +82,7 @@ node. For example, the tutorial uses a machine named `manager1`.
``` ```
The `*` next to the node id, indicates that you're currently connected on The `*` next to the node id indicates that you're currently connected on
this node. this node.
Docker Engine swarm mode automatically names the node for the machine host Docker Engine swarm mode automatically names the node for the machine host