moby/pkg/discovery
Tibor Vass da96e5c27b
Setup tests
Signed-off-by: Tibor Vass <tibor@docker.com>
(cherry picked from commit 8b40da168b)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2019-09-26 23:52:42 +02:00
..
file Setup tests 2019-09-26 23:52:42 +02:00
kv Setup tests 2019-09-26 23:52:42 +02:00
memory Setup tests 2019-09-26 23:52:42 +02:00
nodes Setup tests 2019-09-26 23:52:42 +02:00
backends.go Add canonical import comment 2018-02-05 16:51:57 -05:00
discovery.go Add canonical import comment 2018-02-05 16:51:57 -05:00
discovery_test.go Setup tests 2019-09-26 23:52:42 +02:00
entry.go Add canonical import comment 2018-02-05 16:51:57 -05:00
generator.go Add canonical import comment 2018-02-05 16:51:57 -05:00
generator_test.go rm-gocheck: run goimports to compile successfully 2019-09-26 23:52:28 +02:00
README.md Update docker daemon to dockerd 2016-12-27 17:32:15 +08: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>