From bfdd94b0a8f0641f7bced9d3089a78e9550a7b04 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Wed, 25 Nov 2015 12:38:15 +0100 Subject: [PATCH] Fix markup for markdown table Our tooling used to convert Markdown to HTML doesn't properly handle '|' symbols embeded in code blocks inside a table. Changed the table to a plain HTML table as a workaround. Also fixed indentation levels of two code examples. Signed-off-by: Sebastiaan van Stijn --- docs/userguide/networking/dockernetworks.md | 26 ++++++++++++++++----- 1 file changed, 20 insertions(+), 6 deletions(-) diff --git a/docs/userguide/networking/dockernetworks.md b/docs/userguide/networking/dockernetworks.md index bdc2e85855..fb7d78259f 100644 --- a/docs/userguide/networking/dockernetworks.md +++ b/docs/userguide/networking/dockernetworks.md @@ -420,14 +420,28 @@ form them into a swarm which includes a discovery service as well. To create an overlay network, you configure options on the `daemon` on each Docker Engine for use with `overlay` network. There are two options to set: -| Option | Description | -|-----------------------------------------------|-------------------------------------------------------------| -| `--cluster-store=PROVIDER://URL` | Describes the location of the KV service. | -| `--cluster-advertise=HOST_IP|HOST_IFACE:PORT` | The IP address or interface of the HOST used for clustering | + + + + + + + + + + + + + + + + + +
OptionDescription
--cluster-store=PROVIDER://URL
Describes the location of the KV service.
--cluster-advertise=HOST_IP|HOST_IFACE:PORT
The IP address or interface of the HOST used for clustering.
Create an `overlay` network on one of the machines in the Swarm. - $ docker network create --driver overlay my-multi-host-network + $ docker network create --driver overlay my-multi-host-network This results in a single network spanning multiple hosts. An `overlay` network provides complete isolation for the containers. @@ -436,7 +450,7 @@ provides complete isolation for the containers. Then, on each host, launch containers making sure to specify the network name. - $ docker run -itd --net=my-multi-host-network busybox + $ docker run -itd --net=my-multi-host-network busybox Once connected, each container has access to all the containers in the network regardless of which Docker host the container was launched on.