История

David Calavera 8e034802b7 Remove usage of pkg sockets and tlsconfig. - Use the ones provided by docker/go-connections, they are a drop in replacement. - Remove pkg/sockets from docker. - Keep pkg/tlsconfig because libnetwork still needs it and there is a circular dependency issue. Signed-off-by: David Calavera <david.calavera@gmail.com>		2015-12-29 19:27:12 -05:00
..
file	Add TLS support for discovery backend	2015-10-07 16:01:00 -07:00
kv	Remove usage of pkg sockets and tlsconfig.	2015-12-29 19:27:12 -05:00
nodes	Add TLS support for discovery backend	2015-10-07 16:01:00 -07:00
README.md	…
backends.go	Enhancing --cluster-advertise to support <interface-name>	2015-10-27 11:03:22 -07:00
discovery.go	Add TLS support for discovery backend	2015-10-07 16:01:00 -07:00
discovery_test.go	remove testify asserts from pkg/discovery	2015-10-02 13:05:15 -07:00
entry.go	…
generator.go	…
generator_test.go	remove testify asserts from pkg/discovery	2015-10-02 13:05:15 -07: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.

$ 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>