Browse code

Change NAME to HOSTNAME in docs for `docker node ls`

In #24159, the title field of `docker node ls` has been
changed from NAME to HOSTNAME. However, in the docs the
NAMEs are still used for the output of `docker node ls`.

This fix updates docs so that NAME field is changed to
HOSTNAME for all `docker node ls`.

This fix is related to #24159 and #24090.

Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

Yong Tang authored on 2016/07/07 12:23:53
Showing 7 changed files
... ...
@@ -28,7 +28,7 @@ Lists all the nodes that the Docker Swarm manager knows about. You can filter us
28 28
 Example output:
29 29
 
30 30
     $ docker node ls
31
-    ID                           NAME           MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
31
+    ID                           HOSTNAME        MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
32 32
     1bcef6utixb0l0ca7gxuivsj0    swarm-worker2   Accepted    Ready   Active
33 33
     38ciaotwjuritcdtn9npbnkuz    swarm-worker1   Accepted    Ready   Active
34 34
     e216jshn25ckzbvmwlnh5jr3g *  swarm-manager1  Accepted    Ready   Active        Reachable       Yes
... ...
@@ -52,7 +52,7 @@ The `name` filter matches on all or part of a node name.
52 52
 The following filter matches the node with a name equal to `swarm-master` string.
53 53
 
54 54
     $ docker node ls -f name=swarm-manager1
55
-    ID                           NAME            MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
55
+    ID                           HOSTNAME        MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
56 56
     e216jshn25ckzbvmwlnh5jr3g *  swarm-manager1  Accepted    Ready   Active        Reachable       Yes
57 57
 
58 58
 ### id
... ...
@@ -60,7 +60,7 @@ The following filter matches the node with a name equal to `swarm-master` string
60 60
 The `id` filter matches all or part of a node's id.
61 61
 
62 62
     $ docker node ls -f id=1
63
-    ID                         NAME           MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
63
+    ID                         HOSTNAME       MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
64 64
     1bcef6utixb0l0ca7gxuivsj0  swarm-worker2  Accepted    Ready   Active
65 65
 
66 66
 
... ...
@@ -73,7 +73,7 @@ The following filter matches nodes with the `usage` label regardless of its valu
73 73
 
74 74
 ```bash
75 75
 $ docker node ls -f "label=foo"
76
-ID                         NAME           MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
76
+ID                         HOSTNAME       MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
77 77
 1bcef6utixb0l0ca7gxuivsj0  swarm-worker2  Accepted    Ready   Active
78 78
 ```
79 79
 
... ...
@@ -31,7 +31,7 @@ in the newly created one node Swarm cluster.
31 31
 $ docker swarm init --listen-addr 192.168.99.121:2377
32 32
 Swarm initialized: current node (1ujecd0j9n3ro9i6628smdmth) is now a manager.
33 33
 $ docker node ls
34
-ID                           NAME      MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS          LEADER
34
+ID                           HOSTNAME  MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS          LEADER
35 35
 1ujecd0j9n3ro9i6628smdmth *  manager1  Accepted    Ready   Active        Reachable               Yes
36 36
 ```
37 37
 
... ...
@@ -30,7 +30,7 @@ targeted by this command becomes a `manager`. If it is not specified, it becomes
30 30
 $ docker swarm join --manager --listen-addr 192.168.99.122:2377 192.168.99.121:2377
31 31
 This node joined a Swarm as a manager.
32 32
 $ docker node ls
33
-ID                           NAME      MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS         LEADER
33
+ID                           HOSTNAME  MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS         LEADER
34 34
 dkp8vy1dq1kxleu9g4u78tlag *  manager2  Accepted    Ready   Active        Reachable
35 35
 dvfxp4zseq4s0rih1selh0d20    manager1  Accepted    Ready   Active        Reachable              Yes
36 36
 ```
... ...
@@ -41,7 +41,7 @@ dvfxp4zseq4s0rih1selh0d20    manager1  Accepted    Ready   Active        Reachab
41 41
 $ docker swarm join --listen-addr 192.168.99.123:2377 192.168.99.121:2377
42 42
 This node joined a Swarm as a worker.
43 43
 $ docker node ls
44
-ID                           NAME      MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS         LEADER
44
+ID                           HOSTNAME  MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS         LEADER
45 45
 7ln70fl22uw2dvjn2ft53m3q5    worker2   Accepted    Ready   Active
46 46
 dkp8vy1dq1kxleu9g4u78tlag    worker1   Accepted    Ready   Active        Reachable
47 47
 dvfxp4zseq4s0rih1selh0d20 *  manager1  Accepted    Ready   Active        Reachable              Yes
... ...
@@ -23,7 +23,7 @@ This command causes the node to leave the swarm.
23 23
 On a manager node:
24 24
 ```bash
25 25
 $ docker node ls
26
-ID                           NAME      MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS         LEADER
26
+ID                           HOSTNAME  MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS         LEADER
27 27
 7ln70fl22uw2dvjn2ft53m3q5    worker2   Accepted    Ready   Active
28 28
 dkp8vy1dq1kxleu9g4u78tlag    worker1   Accepted    Ready   Active        Reachable
29 29
 dvfxp4zseq4s0rih1selh0d20 *  manager1  Accepted    Ready   Active        Reachable              Yes
... ...
@@ -38,7 +38,7 @@ Node left the default swarm.
38 38
 On a manager node:
39 39
 ```bash
40 40
 $ docker node ls
41
-ID                           NAME      MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS         LEADER
41
+ID                           HOSTNAME  MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS         LEADER
42 42
 7ln70fl22uw2dvjn2ft53m3q5    worker2   Accepted    Down    Active
43 43
 dkp8vy1dq1kxleu9g4u78tlag    worker1   Accepted    Ready   Active        Reachable
44 44
 dvfxp4zseq4s0rih1selh0d20 *  manager1  Accepted    Ready   Active        Reachable              Yes
... ...
@@ -50,7 +50,7 @@ the existing Swarm.
50 50
 the `docker node ls` command to see the worker nodes:
51 51
 
52 52
     ```bash
53
-    ID                           NAME      MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
53
+    ID                           HOSTNAME  MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
54 54
     03g1y59jwfg7cf99w4lt0f662    worker2   Accepted    Ready   Active
55 55
     9j68exjopxe7wfl6yuxml7a7j    worker1   Accepted    Ready   Active
56 56
     dxn1zf6l61qsb1josjja83ngz *  manager1  Accepted    Ready   Active        Reachable       Yes
... ...
@@ -62,7 +62,7 @@ node. For example, the tutorial uses a machine named `manager1`.
62 62
     ```
63 63
     $ docker node ls
64 64
 
65
-    ID                           NAME      MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
65
+    ID                           HOSTNAME  MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS  LEADER
66 66
     dxn1zf6l61qsb1josjja83ngz *  manager1  Accepted    Ready   Active        Reachable       Yes
67 67
 
68 68
     ```
... ...
@@ -31,7 +31,7 @@ run your manager node. For example, the tutorial uses a machine named
31 31
     ```bash
32 32
     $ docker node ls
33 33
 
34
-    ID                           NAME      MEMBERSHIP  STATUS  AVAILABILITY     MANAGER STATUS  LEADER
34
+    ID                           HOSTNAME  MEMBERSHIP  STATUS  AVAILABILITY     MANAGER STATUS  LEADER
35 35
     1bcef6utixb0l0ca7gxuivsj0    worker2   Accepted    Ready   Active
36 36
     38ciaotwjuritcdtn9npbnkuz    worker1   Accepted    Ready   Active
37 37
     e216jshn25ckzbvmwlnh5jr3g *  manager1  Accepted    Ready   Active        Reachable       Yes