Files
docker-docs/machine/reference/provision.md
Misty Stanley-Jones a4f5e30249 Various copyedits to reduce future tense, wordiness, and use of 'please' (#5788)
* 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
2018-01-25 17:37:23 -08:00

1.2 KiB

description, keywords, title
description keywords title
Re-run provisioning on a created machine. machine, provision, subcommand docker-machine provision

Re-run provisioning on a created machine.

Sometimes it may be helpful to re-run Machine's provisioning process on a created machine. Reasons for doing so may include a failure during the original provisioning process, or a drift from the desired system state (including the originally specified Swarm or Engine configuration).

Usage is docker-machine provision [name]. Multiple names may be specified.

$ docker-machine provision foo bar

Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...

The Machine provisioning process will:

  1. Set the hostname on the instance to the name Machine addresses it by, such as default.
  2. Install Docker if it is not present already.
  3. Generate a set of certificates (usually with the default, self-signed CA) and configure the daemon to accept connections over TLS.
  4. Copy the generated certificates to the server and local config directory.
  5. Configure the Docker Engine according to the options specified at create time.
  6. Configure and activate Swarm if applicable.