mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00

History

Dong Chen 7554e882df Use net.JoinHostPort to handle address format. Signed-off-by: Dong Chen <dongluo.chen@docker.com>		2016-03-01 17:27:30 -08:00
..
file
kv
memory
nodes
backends.go	Use net.JoinHostPort to handle address format.	2016-03-01 17:27:30 -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

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>