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

History

allencloud 1f039a66ac fix typo Signed-off-by: allencloud <allen.sun@daocloud.io>		2016-11-18 15:51:36 +08:00
..
file	all: replace loop with single append	2016-10-13 13:31:52 -07:00
kv	Fix logrus formatting	2016-10-31 22:05:01 -06:00
memory	Fix a race in pkg/discovery/memory	2016-05-25 04:01:43 +00:00
nodes
backends.go	fix typo	2016-11-18 15:51:36 +08:00
discovery.go
discovery_test.go
entry.go
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>