History

Aaron Lehmann 245bd4c3d2 Merge pull request #27365 from morelena/remove_nil_check all: remove nil check for slices		2016-10-13 15:27:37 -07:00
..
file	all: replace loop with single append	2016-10-13 13:31:52 -07:00
kv	Refactoring for logrus formatting	2016-07-18 12:53:34 -06:00
memory	…
nodes	…
README.md	…
backends.go	all: remove nil check for slices	2016-10-13 13:55:38 -07:00
discovery.go	…
discovery_test.go	…
entry.go	…
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>