mirror of https://github.com/docker/docs.git
troubleshooting kramdown issues in a real editor
Signed-off-by: LRubin <lrubin@docker.com>
This commit is contained in:
parent
dce7847515
commit
6976e5912c
|
@ -41,10 +41,12 @@ To generate your access token:
|
|||
|
||||
### Step 3. Use Machine to create the Droplet
|
||||
|
||||
|
||||
1. Run `docker-machine create` with the `digitalocean` driver and pass your key to the `--digitalocean-access-token` flag, along with a name for the new cloud server.
|
||||
|
||||
For this example, we'll call our new Droplet "docker-sandbox".
|
||||
|
||||
```none
|
||||
$ docker-machine create --driver digitalocean --digitalocean-access-token xxxxx docker-sandbox
|
||||
Running pre-create checks...
|
||||
Creating machine...
|
||||
|
@ -60,6 +62,7 @@ To generate your access token:
|
|||
Copying certs to the remote machine...
|
||||
Setting Docker configuration on the remote daemon...
|
||||
To see how to connect Docker to this machine, run: docker-machine env docker-sandbox
|
||||
```
|
||||
|
||||
When the Droplet is created, Docker generates a unique SSH key and stores it on your local system in `~/.docker/machines`. Initially, this is used to provision the host. Later, it's used under the hood to access the Droplet directly with the `docker-machine ssh` command. Docker Engine is installed on the cloud server and the daemon is configured to accept remote connections over TCP using TLS for authentication.
|
||||
|
||||
|
|
Loading…
Reference in New Issue