docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: simplify some steps of the overlay network guide 

Instead of using a process expansion to feed the right arguments to
docker to run on "mh-keystore", just moves up the next step which makes
"mh-keystore" the default target. This makes the guide a bit shorter and
easier to understand.

Signed-off-by: Vincent Bernat <vincent@bernat.im>
This commit is contained in:
Vincent Bernat 2016-02-25 11:46:27 +01:00
parent 7cf03700f8
commit db5ded0dfc
1 changed files with 9 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/userguide/networking/get-started-overlay.md
View File

@ -55,21 +55,20 @@ key-value stores. This example uses Consul.
instance using the [consul image from Docker instance using the [consul image from Docker
Hub](https://hub.docker.com/r/progrium/consul/). You'll do this in the next step. Hub](https://hub.docker.com/r/progrium/consul/). You'll do this in the next step.
3. Start a `progrium/consul` container running on the `mh-keystore` machine. 3. Set your local environment to the `mh-keystore` machine.
$ docker $(docker-machine config mh-keystore) run -d \ $ eval "$(docker-machine env mh-keystore)"
4. Start a `progrium/consul` container running on the `mh-keystore` machine.
$ docker run -d \
-p "8500:8500" \ -p "8500:8500" \
-h "consul" \ -h "consul" \
progrium/consul -server -bootstrap progrium/consul -server -bootstrap
A bash expansion `$(docker-machine config mh-keystore)` is used to pass the The client starts a `progrium/consul` image running in the
connection configuration to the `docker run` command. The client starts a `mh-keystore` machine. The server is called `consul` and is
`progrium/consul` image running in the `mh-keystore` machine. The server is listening on port `8500`.
called `consul` and is listening on port `8500`.
4. Set your local environment to the `mh-keystore` machine.
$ eval "$(docker-machine env mh-keystore)"
5. Run the `docker ps` command to see the `consul` container. 5. Run the `docker ps` command to see the `consul` container.