reg/vendor/github.com/docker/docker-ce/components/engine/pkg/discovery
Jess Frazelle 843aebf2c1
update deps
Signed-off-by: Jess Frazelle <acidburn@microsoft.com>
2018-07-14 11:48:41 -04:00
..
file update deps 2018-07-14 11:48:41 -04:00
kv update deps 2018-07-14 11:48:41 -04:00
memory update deps 2018-07-14 11:48:41 -04:00
nodes update deps 2018-07-14 11:48:41 -04:00
backends.go update deps 2018-07-14 11:48:41 -04:00
discovery.go update deps 2018-07-14 11:48:41 -04:00
discovery_test.go update deps 2018-07-14 11:48:41 -04:00
entry.go update deps 2018-07-14 11:48:41 -04:00
generator.go update deps 2018-07-14 11:48:41 -04:00
generator_test.go update deps 2018-07-14 11:48:41 -04:00
README.md update deps 2018-07-14 11:48:41 -04:00

page_title page_description page_keywords
Docker discovery discovery docker, clustering, discovery

Discovery

Docker comes with multiple Discovery backends.

Backends

Using etcd

Point your Docker Engine instances to a common etcd instance. You can specify the address Docker uses to advertise the node using the --cluster-advertise flag.

$ dockerd -H=<node_ip:2376> --cluster-advertise=<node_ip:2376> --cluster-store etcd://<etcd_ip1>,<etcd_ip2>/<path>

Using consul

Point your Docker Engine instances to a common Consul instance. You can specify the address Docker uses to advertise the node using the --cluster-advertise flag.

$ dockerd -H=<node_ip:2376> --cluster-advertise=<node_ip:2376> --cluster-store consul://<consul_ip>/<path>

Using zookeeper

Point your Docker Engine instances to a common Zookeeper instance. You can specify the address Docker uses to advertise the node using the --cluster-advertise flag.

$ dockerd -H=<node_ip:2376> --cluster-advertise=<node_ip:2376> --cluster-store zk://<zk_addr1>,<zk_addr2>/<path>