mirror of
https://github.com/docker/docs.git
synced 2026-03-27 22:38:54 +07:00
a4f5e30249
* Reword lots of instances of 'will' * Reword lots of instances of won't * Reword lots of instances of we'll * Eradicate you'll * Eradicate 'be able to' type of phrases * Eradicate 'unable to' type of phrases * Eradicate 'has / have to' type of phrases * Eradicate 'note that' type of phrases * Eradicate 'in order to' type of phrases * Redirect to official Chef and Puppet docs * Eradicate gratuitous 'please' * Reduce use of e.g. * Reduce use of i.e. * Reduce use of N.B. * Get rid of 'sexagesimal' and correct some errors
1.0 KiB
1.0 KiB
advisory, hide_from_sitemap, description, keywords, title
| advisory | hide_from_sitemap | description | keywords | title |
|---|---|---|---|---|
| swarm-standalone | true | Create a Swarm manager. | swarm, create | create — Create a discovery token |
The create command uses Docker Hub's hosted discovery backend to create a unique discovery token for your cluster. For example:
$ docker run --rm swarm create
86222732d62b6868d441d430aee4f055
Later, when you use manage or join to create Swarm managers and nodes, you use the discovery token in the <discovery> argument. For instance, token://86222732d62b6868d441d430aee4f055. The discovery backend registers each new Swarm manager and node that uses the token as a member of your cluster.
Some documentation also refers to the discovery token as a cluster_id.
Warning
: Docker Hub's hosted discovery backend is not recommended for production use. It’s intended only for testing/development.
For more information and examples about this and other discovery backends, see the Docker Swarm Discovery topic.