mirror of
https://github.com/moby/moby.git
synced 2026-07-12 18:45:06 +00:00
eb67bb9fb5
sed -E -i 's#([^*])(check\.TestingT\([^\)]+\))#\1/*\2*/#g' \ -- "integration-cli/check_test.go" "pkg/discovery/discovery_test.go" "pkg/discovery/file/file_test.go" "pkg/discovery/kv/kv_test.go" "pkg/discovery/memory/memory_test.go" "pkg/discovery/nodes/nodes_test.go" Signed-off-by: Tibor Vass <tibor@docker.com>
page_title, page_description, page_keywords
| 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.
$ dockerd -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.
$ dockerd -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.
$ dockerd -H=<node_ip:2376> --cluster-advertise=<node_ip:2376> --cluster-store zk://<zk_addr1>,<zk_addr2>/<path>