History

allencloud d0081a0f47 better command `docker network create -h` output Signed-off-by: allencloud <allen.sun@daocloud.io>		2016-07-16 15:32:17 +08:00
..
file	…
kv	Fix too short time.Sleep() in pkg/discovery/kv/kv_test.go	2016-05-27 04:08:55 +00:00
memory	Fix a race in pkg/discovery/memory	2016-05-25 04:01:43 +00:00
nodes	…
README.md	…
backends.go	better command `docker network create -h` output	2016-07-16 15:32:17 +08:00
discovery.go	…
discovery_test.go	Handle IPv6 entries.	2016-03-01 16:56:12 -08:00
entry.go	Handle IPv6 entries.	2016-03-01 16:56:12 -08:00
generator.go	…
generator_test.go	…

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.

$ docker daemon -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.

$ docker daemon -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.

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