Browse code
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>
Vincent Bernat authored on 2016/02/25 19:46:27Showing 1 changed files
| ... | ... |
@@ -55,21 +55,20 @@ key-value stores. This example uses Consul. |
| 55 | 55 |
instance using the [consul image from Docker |
| 56 | 56 |
Hub](https://hub.docker.com/r/progrium/consul/). You'll do this in the next step. |
| 57 | 57 |
|
| 58 |
-3. Start a `progrium/consul` container running on the `mh-keystore` machine. |
|
| 58 |
+3. Set your local environment to the `mh-keystore` machine. |
|
| 59 | 59 |
|
| 60 |
- $ docker $(docker-machine config mh-keystore) run -d \ |
|
| 60 |
+ $ eval "$(docker-machine env mh-keystore)" |
|
| 61 |
+ |
|
| 62 |
+4. Start a `progrium/consul` container running on the `mh-keystore` machine. |
|
| 63 |
+ |
|
| 64 |
+ $ docker run -d \ |
|
| 61 | 65 |
-p "8500:8500" \ |
| 62 | 66 |
-h "consul" \ |
| 63 | 67 |
progrium/consul -server -bootstrap |
| 64 | 68 |
|
| 65 |
- A bash expansion `$(docker-machine config mh-keystore)` is used to pass the |
|
| 66 |
- connection configuration to the `docker run` command. The client starts a |
|
| 67 |
- `progrium/consul` image running in the `mh-keystore` machine. The server is |
|
| 68 |
- called `consul` and is listening on port `8500`. |
|
| 69 |
- |
|
| 70 |
-4. Set your local environment to the `mh-keystore` machine. |
|
| 71 |
- |
|
| 72 |
- $ eval "$(docker-machine env mh-keystore)" |
|
| 69 |
+ The client starts a `progrium/consul` image running in the |
|
| 70 |
+ `mh-keystore` machine. The server is called `consul` and is |
|
| 71 |
+ listening on port `8500`. |
|
| 73 | 72 |
|
| 74 | 73 |
5. Run the `docker ps` command to see the `consul` container. |
| 75 | 74 |
|