mirror of https://github.com/docker/docs.git
clarify discovery service information
- specify that we need to use a discovery service - indicate which specific discovery service we are using for this example - describe the token discovery service as hosted at Docker Hub - link to other available discovery services in the docs Signed-off-by: Morgan Bauer <mbauer@us.ibm.com>
This commit is contained in:
parent
b154ccb585
commit
6d8fea0664
|
|
@ -33,9 +33,12 @@ Docker Machine gets hosts ready to run Docker containers. Each node in your
|
||||||
Docker Swarm must have access to Docker to pull images and run them in
|
Docker Swarm must have access to Docker to pull images and run them in
|
||||||
containers. Docker Machine manages all this provisioning for your swarm.
|
containers. Docker Machine manages all this provisioning for your swarm.
|
||||||
|
|
||||||
Before you create a swarm with `docker-machine`, you create a discovery token.
|
Before you create a swarm with `docker-machine`, you associate each
|
||||||
Docker Swarm uses tokens for discovery and agent registration. Using this token,
|
node with a discovery service. This example uses the token discovery
|
||||||
you can create a swarm that is secured.
|
service hosted by Docker Hub. This discovery service associates a
|
||||||
|
token with instances of the Docker Daemon running on each node. Other
|
||||||
|
discovery service backends such as `etcd`, `consul`, and `zookeeper`
|
||||||
|
are [available](/discovery).
|
||||||
|
|
||||||
1. List the machines on your system.
|
1. List the machines on your system.
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue