improve example run commands in docker_guide

When bootstrapping a cluster, the docker run command is mostly the same for all cluster member. This commits highlight the small variations between the commands to make them stand out.
This commit is contained in:
tobilarscheid 2017-01-12 09:16:21 +01:00 committed by GitHub
parent 8adfc06084
commit c624caabb1

View File

@ -44,48 +44,48 @@ The main difference being the value used for the `-initial-cluster` flag, which
### etcd0 ### etcd0
``` <pre>
docker run -d -v /usr/share/ca-certificates/:/etc/ssl/certs -p 4001:4001 -p 2380:2380 -p 2379:2379 \ docker run -d -v /usr/share/ca-certificates/:/etc/ssl/certs -p 4001:4001 -p 2380:2380 -p 2379:2379 \
--name etcd quay.io/coreos/etcd \ --name etcd quay.io/coreos/etcd \
-name etcd0 \ <b>-name etcd0</b> \
-advertise-client-urls http://192.168.12.50:2379,http://192.168.12.50:4001 \ <b>-advertise-client-urls http://192.168.12.50:2379,http://192.168.12.50:4001</b> \
-listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 \ -listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 \
-initial-advertise-peer-urls http://192.168.12.50:2380 \ <b>-initial-advertise-peer-urls http://192.168.12.50:2380</b> \
-listen-peer-urls http://0.0.0.0:2380 \ -listen-peer-urls http://0.0.0.0:2380 \
-initial-cluster-token etcd-cluster-1 \ -initial-cluster-token etcd-cluster-1 \
-initial-cluster etcd0=http://192.168.12.50:2380,etcd1=http://192.168.12.51:2380,etcd2=http://192.168.12.52:2380 \ -initial-cluster etcd0=http://192.168.12.50:2380,etcd1=http://192.168.12.51:2380,etcd2=http://192.168.12.52:2380 \
-initial-cluster-state new -initial-cluster-state new
``` </pre>
### etcd1 ### etcd1
``` <pre>
docker run -d -v /usr/share/ca-certificates/:/etc/ssl/certs -p 4001:4001 -p 2380:2380 -p 2379:2379 \ docker run -d -v /usr/share/ca-certificates/:/etc/ssl/certs -p 4001:4001 -p 2380:2380 -p 2379:2379 \
--name etcd quay.io/coreos/etcd \ --name etcd quay.io/coreos/etcd \
-name etcd1 \ <b>-name etcd1</b> \
-advertise-client-urls http://192.168.12.51:2379,http://192.168.12.51:4001 \ <b>-advertise-client-urls http://192.168.12.51:2379,http://192.168.12.51:4001</b> \
-listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 \ -listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 \
-initial-advertise-peer-urls http://192.168.12.51:2380 \ <b>-initial-advertise-peer-urls http://192.168.12.51:2380</b> \
-listen-peer-urls http://0.0.0.0:2380 \ -listen-peer-urls http://0.0.0.0:2380 \
-initial-cluster-token etcd-cluster-1 \ -initial-cluster-token etcd-cluster-1 \
-initial-cluster etcd0=http://192.168.12.50:2380,etcd1=http://192.168.12.51:2380,etcd2=http://192.168.12.52:2380 \ -initial-cluster etcd0=http://192.168.12.50:2380,etcd1=http://192.168.12.51:2380,etcd2=http://192.168.12.52:2380 \
-initial-cluster-state new -initial-cluster-state new
``` </pre>
### etcd2 ### etcd2
``` <pre>
docker run -d -v /usr/share/ca-certificates/:/etc/ssl/certs -p 4001:4001 -p 2380:2380 -p 2379:2379 \ docker run -d -v /usr/share/ca-certificates/:/etc/ssl/certs -p 4001:4001 -p 2380:2380 -p 2379:2379 \
--name etcd quay.io/coreos/etcd \ --name etcd quay.io/coreos/etcd \
-name etcd2 \ <b>-name etcd2</b> \
-advertise-client-urls http://192.168.12.52:2379,http://192.168.12.52:4001 \ <b>-advertise-client-urls http://192.168.12.52:2379,http://192.168.12.52:4001</b> \
-listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 \ -listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 \
-initial-advertise-peer-urls http://192.168.12.52:2380 \ <b>-initial-advertise-peer-urls http://192.168.12.52:2380</b> \
-listen-peer-urls http://0.0.0.0:2380 \ -listen-peer-urls http://0.0.0.0:2380 \
-initial-cluster-token etcd-cluster-1 \ -initial-cluster-token etcd-cluster-1 \
-initial-cluster etcd0=http://192.168.12.50:2380,etcd1=http://192.168.12.51:2380,etcd2=http://192.168.12.52:2380 \ -initial-cluster etcd0=http://192.168.12.50:2380,etcd1=http://192.168.12.51:2380,etcd2=http://192.168.12.52:2380 \
-initial-cluster-state new -initial-cluster-state new
``` </pre>
Once the cluster has been bootstrapped etcd clients can be configured with a list of etcd members: Once the cluster has been bootstrapped etcd clients can be configured with a list of etcd members: