History

luoyaoming 46a93db995 Import Upstream version 20.10.16		2022-12-16 13:24:03 +08:00
..
file	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
kv	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
memory	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
nodes	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
README.md	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
backends.go	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
discovery.go	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
discovery_test.go	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
entry.go	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
generator.go	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00
generator_test.go	Import Upstream version 20.10.16	2022-12-16 13:24:03 +08:00

README.md

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>