mirror of
https://github.com/clearlinux/docker.git
synced 2026-09-06 13:41:36 +00:00
Networking API and UX documentation
More doc updates will follow Signed-off-by: Madhu Venugopal <madhu@docker.com>
This commit is contained in:
Madhu Venugopal
@@ -2,7 +2,7 @@
|
||||
+++
|
||||
title = "Network configuration"
|
||||
description = "Docker networking"
|
||||
keywords = ["network, networking, bridge, docker, documentation"]
|
||||
keywords = ["network, networking, bridge, overlay, cluster, multihost, docker, documentation"]
|
||||
[menu.main]
|
||||
parent= "smn_administrate"
|
||||
+++
|
||||
@@ -10,6 +10,9 @@ parent= "smn_administrate"
|
||||
|
||||
# Network configuration
|
||||
|
||||
> **Note:**
|
||||
> This document is outdated and needs a major overhaul.
|
||||
|
||||
## Summary
|
||||
|
||||
When Docker starts, it creates a virtual interface named `docker0` on
|
||||
|
||||
@@ -15,6 +15,7 @@ weight = 6
|
||||
|
||||
Currently, you can extend Docker by adding a plugin. This section contains the following topics:
|
||||
|
||||
* [Understand Docker plugins](/extend/plugins)
|
||||
* [Write a volume plugin](/extend/plugins_volume)
|
||||
* [Docker plugin API](/extend/plugin_api)
|
||||
* [Understand Docker plugins](/extend/plugins.md)
|
||||
* [Write a volume plugin](/extend/plugins_volume.md)
|
||||
* [Write a network plugin](/extend/plugins_network.md)
|
||||
* [Docker plugin API](/extend/plugin_api.md)
|
||||
|
||||
@@ -17,8 +17,10 @@ plugins.
|
||||
## Types of plugins
|
||||
|
||||
Plugins extend Docker's functionality. They come in specific types. For
|
||||
example, a [volume plugin](/extend/plugins_volume) might enable Docker
|
||||
volumes to persist across multiple Docker hosts.
|
||||
example, a [volume plugin](/extend/plugins_volume.md) might enable Docker
|
||||
volumes to persist across multiple Docker hosts and a
|
||||
[network plugin](/extend/plugins_network.md) might provide network plumbing
|
||||
using a favorite networking technology, such as vxlan overlay, ipvlan, EVPN, etc.
|
||||
|
||||
Currently Docker supports volume and network driver plugins. In the future it
|
||||
will support additional plugin types.
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
# Docker network driver plugins
|
||||
|
||||
Docker supports network driver plugins via
|
||||
[LibNetwork](https://github.com/docker/libnetwork). Network driver plugins are
|
||||
implemented as "remote drivers" for LibNetwork, which shares plugin
|
||||
infrastructure with Docker. In effect this means that network driver plugins
|
||||
are activated in the same way as other plugins, and use the same kind of
|
||||
protocol.
|
||||
|
||||
## Using network driver plugins
|
||||
|
||||
The means of installing and running a network driver plugin will depend on the
|
||||
particular plugin.
|
||||
|
||||
Once running however, network driver plugins are used just like the built-in
|
||||
network drivers: by being mentioned as a driver in network-oriented Docker
|
||||
commands. For example,
|
||||
|
||||
docker network create -d weave mynet
|
||||
|
||||
Some network driver plugins are listed in [plugins.md](/docs/extend/plugins.md)
|
||||
|
||||
The network thus created is owned by the plugin, so subsequent commands
|
||||
referring to that network will also be run through the plugin such as,
|
||||
|
||||
docker run --net=mynet busybox top
|
||||
|
||||
## Network driver plugin protocol
|
||||
|
||||
The network driver protocol, additional to the plugin activation call, is
|
||||
documented as part of LibNetwork:
|
||||
[https://github.com/docker/libnetwork/blob/master/docs/remote.md](https://github.com/docker/libnetwork/blob/master/docs/remote.md).
|
||||
|
||||
# Related GitHub PRs and issues
|
||||
|
||||
Please record your feedback in the following issue, on the usual
|
||||
Google Groups, or the IRC channel #docker-network.
|
||||
|
||||
- [#14083](https://github.com/docker/docker/issues/14083) Feedback on
|
||||
experimental networking features
|
||||
@@ -2484,6 +2484,218 @@ Status Codes
|
||||
- **409** - volume is in use and cannot be removed
|
||||
- **500** - server error
|
||||
|
||||
## 2.5 Networks
|
||||
|
||||
### List networks
|
||||
|
||||
`GET /networks`
|
||||
|
||||
**Example request**:
|
||||
|
||||
GET /networks HTTP/1.1
|
||||
|
||||
**Example response**:
|
||||
|
||||
HTTP/1.1 200 OK
|
||||
Content-Type: application/json
|
||||
|
||||
```
|
||||
[
|
||||
{
|
||||
"name": "bridge",
|
||||
"id": "f995e41e471c833266786a64df584fbe4dc654ac99f63a4ee7495842aa093fc4",
|
||||
"driver": "bridge"
|
||||
},
|
||||
{
|
||||
"name": "none",
|
||||
"id": "21e34df9b29c74ae45ba312f8e9f83c02433c9a877cfebebcf57be78f69b77c8",
|
||||
"driver": "null"
|
||||
},
|
||||
{
|
||||
"name": "host",
|
||||
"id": "3f43a0873f00310a71cd6a71e2e60c113cf17d1812be2ec22fd519fbac68ec91",
|
||||
"driver": "host"
|
||||
}
|
||||
]
|
||||
```
|
||||
|
||||
|
||||
|
||||
Query Parameters:
|
||||
|
||||
- **filter** - JSON encoded value of the filters (a `map[string][]string`) to process on the volumes list. Available filters: `name=[network-names]` , `id=[network-ids]`
|
||||
|
||||
Status Codes:
|
||||
|
||||
- **200** - no error
|
||||
- **500** - server error
|
||||
|
||||
### Inspect network
|
||||
|
||||
`GET /networks/<network-id>`
|
||||
|
||||
**Example request**:
|
||||
|
||||
GET /networks/f995e41e471c833266786a64df584fbe4dc654ac99f63a4ee7495842aa093fc4 HTTP/1.1
|
||||
|
||||
**Example response**:
|
||||
|
||||
HTTP/1.1 200 OK
|
||||
Content-Type: application/json
|
||||
|
||||
```
|
||||
{
|
||||
"name": "bridge",
|
||||
"id": "f995e41e471c833266786a64df584fbe4dc654ac99f63a4ee7495842aa093fc4",
|
||||
"driver": "bridge",
|
||||
"containers": {
|
||||
"931d29e96e63022a3691f55ca18b28600239acf53878451975f77054b05ba559": {
|
||||
"endpoint": "aa79321e2899e6d72fcd46e6a4ad7f81ab9a19c3b06e384ef4ce51fea35827f9",
|
||||
"mac_address": "02:42:ac:11:00:04",
|
||||
"ipv4_address": "172.17.0.4/16"
|
||||
},
|
||||
"961249b4ae6c764b11eed923e8463c102689111fffd933627b2e7e359c7d0f7c": {
|
||||
"endpoint": "4f62c5aea6b9a70512210be7db976bd4ec2cdba47125e4fe514d18c81b1624b1",
|
||||
"mac_address": "02:42:ac:11:00:02",
|
||||
"ipv4_address": "172.17.0.2/16"
|
||||
},
|
||||
"9f6e0fec4449f42a173ed85be96dc2253b6719edd850d8169bc31bdc45db675c": {
|
||||
"endpoint": "352b512a5bccdfc77d16c2c04d04408e718f879a16f9ce3913a4733139e4f98d",
|
||||
"mac_address": "02:42:ac:11:00:03",
|
||||
"ipv4_address": "172.17.0.3/16"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Status Codes:
|
||||
|
||||
- **200** - no error
|
||||
- **404** - network not found
|
||||
|
||||
### Create a network
|
||||
|
||||
`POST /networks/create`
|
||||
|
||||
Create a network
|
||||
|
||||
**Example request**:
|
||||
|
||||
POST /networks/create HTTP/1.1
|
||||
Content-Type: application/json
|
||||
|
||||
```
|
||||
{
|
||||
"name":"isolated_nw",
|
||||
"driver":"bridge"
|
||||
}
|
||||
```
|
||||
|
||||
**Example response**:
|
||||
|
||||
HTTP/1.1 201 Created
|
||||
Content-Type: application/json
|
||||
|
||||
```
|
||||
{
|
||||
"id": "22be93d5babb089c5aab8dbc369042fad48ff791584ca2da2100db837a1c7c30",
|
||||
"warning": ""
|
||||
}
|
||||
```
|
||||
|
||||
Status Codes:
|
||||
|
||||
- **201** - no error
|
||||
- **404** - driver not found
|
||||
- **500** - server error
|
||||
|
||||
JSON Parameters:
|
||||
|
||||
- **name** - The new network's name. this is a mandatory field
|
||||
- **driver** - Name of the network driver to use. Defaults to `bridge` driver
|
||||
- **options** - Network specific options to be used by the drivers
|
||||
- **check_duplicate** - Requests daemon to check for networks with same name
|
||||
|
||||
### Connect a container to a network
|
||||
|
||||
`POST /networks/(id)/connect`
|
||||
|
||||
Connects a container to a network
|
||||
|
||||
**Example request**:
|
||||
|
||||
POST /networks/22be93d5babb089c5aab8dbc369042fad48ff791584ca2da2100db837a1c7c30/connect HTTP/1.1
|
||||
Content-Type: application/json
|
||||
|
||||
```
|
||||
{
|
||||
"container":"3613f73ba0e4"
|
||||
}
|
||||
```
|
||||
|
||||
**Example response**:
|
||||
|
||||
HTTP/1.1 200 OK
|
||||
|
||||
Status Codes:
|
||||
|
||||
- **201** - no error
|
||||
- **404** - network or container is not found
|
||||
|
||||
JSON Parameters:
|
||||
|
||||
- **container** - container-id/name to be connected to the network
|
||||
|
||||
### Disconnect a container from a network
|
||||
|
||||
`POST /networks/(id)/disconnect`
|
||||
|
||||
Disconnects a container from a network
|
||||
|
||||
**Example request**:
|
||||
|
||||
POST /networks/22be93d5babb089c5aab8dbc369042fad48ff791584ca2da2100db837a1c7c30/disconnect HTTP/1.1
|
||||
Content-Type: application/json
|
||||
|
||||
```
|
||||
{
|
||||
"container":"3613f73ba0e4"
|
||||
}
|
||||
```
|
||||
|
||||
**Example response**:
|
||||
|
||||
HTTP/1.1 200 OK
|
||||
|
||||
Status Codes:
|
||||
|
||||
- **201** - no error
|
||||
- **404** - network or container not found
|
||||
|
||||
JSON Parameters:
|
||||
|
||||
- **container** - container-id/name to be disconnected from a network
|
||||
|
||||
### Remove a network
|
||||
|
||||
`DELETE /networks/(id)`
|
||||
|
||||
Instruct the driver to remove the network (`id`).
|
||||
|
||||
**Example request**:
|
||||
|
||||
DELETE /networks/22be93d5babb089c5aab8dbc369042fad48ff791584ca2da2100db837a1c7c30 HTTP/1.1
|
||||
|
||||
**Example response**:
|
||||
|
||||
HTTP/1.1 204 No Content
|
||||
|
||||
Status Codes
|
||||
|
||||
- **204** - no error
|
||||
- **404** - no such network
|
||||
- **500** - server error
|
||||
|
||||
# 3. Going further
|
||||
|
||||
## 3.1 Inside `docker run`
|
||||
|
||||
@@ -0,0 +1,30 @@
|
||||
<!--[metadata]>
|
||||
+++
|
||||
title = "network connect"
|
||||
description = "The network connect command description and usage"
|
||||
keywords = ["network, connect"]
|
||||
[menu.main]
|
||||
parent = "smn_cli"
|
||||
+++
|
||||
<![end-metadata]-->
|
||||
|
||||
# network connect
|
||||
|
||||
Usage: docker network connect [OPTIONS] NETWORK CONTAINER
|
||||
|
||||
Connects a container to a network
|
||||
|
||||
--help=false Print usage
|
||||
|
||||
Connects a running container to a network. This enables instant communication with other containers belonging to the same network.
|
||||
|
||||
```
|
||||
$ docker network create -d overlay multi-host-network
|
||||
$ docker run -d --name=container1 busybox top
|
||||
$ docker network connect multi-host-network container1
|
||||
```
|
||||
|
||||
the container will be connected to the network that is created and managed by the driver (multi-host overlay driver in the above example) or external network plugins.
|
||||
|
||||
Multiple containers can be connected to the same network and the containers in the same network will start to communicate with each other. If the driver/plugin supports multi-host connectivity, then the containers connected to the same multi-host network will be able to communicate seamlessly.
|
||||
|
||||
@@ -0,0 +1,32 @@
|
||||
<!--[metadata]>
|
||||
+++
|
||||
title = "network create"
|
||||
description = "The network create command description and usage"
|
||||
keywords = ["network, create"]
|
||||
[menu.main]
|
||||
parent = "smn_cli"
|
||||
+++
|
||||
<![end-metadata]-->
|
||||
|
||||
# network create
|
||||
|
||||
Usage: docker network create [OPTIONS] NETWORK-NAME
|
||||
|
||||
Creates a new network with a name specified by the user
|
||||
|
||||
-d, --driver= Driver to manage the Network
|
||||
--help=false Print usage
|
||||
|
||||
Creates a new network that containers can connect to. If the driver supports multi-host networking, the created network will be made available across all the hosts in the cluster. Daemon will do its best to identify network name conflicts. But its the users responsibility to make sure network name is unique across the cluster. You create a network and then configure the container to use it, for example:
|
||||
|
||||
```
|
||||
$ docker network create -d overlay multi-host-network
|
||||
$ docker run -itd --net=multi-host-network busybox
|
||||
```
|
||||
|
||||
the container will be connected to the network that is created and managed by the driver (multi-host overlay driver in the above example) or external network plugins.
|
||||
|
||||
Multiple containers can be connected to the same network and the containers in the same network will start to communicate with each other. If the driver/plugin supports multi-host connectivity, then the containers connected to the same multi-host network will be able to communicate seamlessly.
|
||||
|
||||
*Note*: UX needs enhancement to accept network options to be passed to the drivers
|
||||
|
||||
@@ -0,0 +1,27 @@
|
||||
<!--[metadata]>
|
||||
+++
|
||||
title = "network disconnect"
|
||||
description = "The network disconnect command description and usage"
|
||||
keywords = ["network, disconnect"]
|
||||
[menu.main]
|
||||
parent = "smn_cli"
|
||||
+++
|
||||
<![end-metadata]-->
|
||||
|
||||
# network disconnect
|
||||
|
||||
Usage: docker network disconnect [OPTIONS] NETWORK CONTAINER
|
||||
|
||||
Disconnects a container from a network
|
||||
|
||||
--help=false Print usage
|
||||
|
||||
Disconnects a running container from a network.
|
||||
|
||||
```
|
||||
$ docker network create -d overlay multi-host-network
|
||||
$ docker run -d --net=multi-host-network --name=container1 busybox top
|
||||
$ docker network disconnect multi-host-network container1
|
||||
```
|
||||
|
||||
the container will be disconnected from the network.
|
||||
@@ -0,0 +1,49 @@
|
||||
<!--[metadata]>
|
||||
+++
|
||||
title = "network inspect"
|
||||
description = "The network inspect command description and usage"
|
||||
keywords = ["network, inspect"]
|
||||
[menu.main]
|
||||
parent = "smn_cli"
|
||||
+++
|
||||
<![end-metadata]-->
|
||||
|
||||
# network inspect
|
||||
|
||||
Usage: docker network inspect [OPTIONS] NETWORK
|
||||
|
||||
Displays detailed information on a network
|
||||
|
||||
--help=false Print usage
|
||||
|
||||
Returns information about a network. By default, this command renders all results
|
||||
in a JSON object.
|
||||
|
||||
Example output:
|
||||
|
||||
```
|
||||
$ sudo docker run -itd --name=container1 busybox
|
||||
f2870c98fd504370fb86e59f32cd0753b1ac9b69b7d80566ffc7192a82b3ed27
|
||||
|
||||
$ sudo docker run -itd --name=container2 busybox
|
||||
bda12f8922785d1f160be70736f26c1e331ab8aaf8ed8d56728508f2e2fd4727
|
||||
|
||||
$ sudo docker network inspect bridge
|
||||
{
|
||||
"name": "bridge",
|
||||
"id": "7fca4eb8c647e57e9d46c32714271e0c3f8bf8d17d346629e2820547b2d90039",
|
||||
"driver": "bridge",
|
||||
"containers": {
|
||||
"bda12f8922785d1f160be70736f26c1e331ab8aaf8ed8d56728508f2e2fd4727": {
|
||||
"endpoint": "e0ac95934f803d7e36384a2029b8d1eeb56cb88727aa2e8b7edfeebaa6dfd758",
|
||||
"mac_address": "02:42:ac:11:00:03",
|
||||
"ipv4_address": "172.17.0.3/16"
|
||||
},
|
||||
"f2870c98fd504370fb86e59f32cd0753b1ac9b69b7d80566ffc7192a82b3ed27": {
|
||||
"endpoint": "31de280881d2a774345bbfb1594159ade4ae4024ebfb1320cb74a30225f6a8ae",
|
||||
"mac_address": "02:42:ac:11:00:02",
|
||||
"ipv4_address": "172.17.0.2/16"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,32 @@
|
||||
<!--[metadata]>
|
||||
+++
|
||||
title = "network ls"
|
||||
description = "The network ls command description and usage"
|
||||
keywords = ["network, list"]
|
||||
[menu.main]
|
||||
parent = "smn_cli"
|
||||
+++
|
||||
<![end-metadata]-->
|
||||
|
||||
# docker network ls
|
||||
|
||||
Usage: docker network ls [OPTIONS]
|
||||
|
||||
Lists all the networks created by the user
|
||||
--help=false Print usage
|
||||
-l, --latest=false Show the latest network created
|
||||
-n=-1 Show n last created networks
|
||||
--no-trunc=false Do not truncate the output
|
||||
-q, --quiet=false Only display numeric IDs
|
||||
|
||||
Lists all the networks Docker knows about. This include the networks that spans across multiple hosts in a cluster.
|
||||
|
||||
Example output:
|
||||
|
||||
```
|
||||
$ sudo docker network ls
|
||||
NETWORK ID NAME DRIVER
|
||||
7fca4eb8c647 bridge bridge
|
||||
9f904ee27bf5 none null
|
||||
cf03ee007fb4 host host
|
||||
```
|
||||
@@ -0,0 +1,23 @@
|
||||
<!--[metadata]>
|
||||
+++
|
||||
title = "network rm"
|
||||
description = "the network rm command description and usage"
|
||||
keywords = ["network, rm"]
|
||||
[menu.main]
|
||||
parent = "smn_cli"
|
||||
+++
|
||||
<![end-metadata]-->
|
||||
|
||||
# network rm
|
||||
|
||||
Usage: docker network rm [OPTIONS] NETWORK
|
||||
|
||||
Deletes a network
|
||||
|
||||
--help=false Print usage
|
||||
|
||||
Removes a network. You cannot remove a network that is in use by 1 or more containers.
|
||||
|
||||
```
|
||||
$ docker network rm my-network
|
||||
```
|
||||
@@ -132,6 +132,12 @@ namespaces, cgroups, capabilities, and filesystem access controls. It allows
|
||||
you to manage the lifecycle of the container performing additional operations
|
||||
after the container is created.
|
||||
|
||||
## libnetwork
|
||||
|
||||
libnetwork provides a native Go implementation for creating and managing container
|
||||
network namespaces and other network resources. It manage the networking lifecycle
|
||||
of the container performing additional operations after the container is created.
|
||||
|
||||
## link
|
||||
|
||||
links provide an interface to connect Docker containers running on the same host
|
||||
@@ -149,7 +155,12 @@ installs Docker on them, then configures the Docker client to talk to them.
|
||||
|
||||
*Also known as : docker-machine*
|
||||
|
||||
## overlay
|
||||
## overlay network driver
|
||||
|
||||
Overlay network driver provides out of the box multi-host network connectivity
|
||||
for docker containers in a cluster.
|
||||
|
||||
## overlay storage driver
|
||||
|
||||
OverlayFS is a [filesystem](#filesystem) service for Linux which implements a
|
||||
[union mount](http://en.wikipedia.org/wiki/Union_mount) for other file systems.
|
||||
|
||||
+33
-11
@@ -245,11 +245,12 @@ of the containers.
|
||||
## Network settings
|
||||
|
||||
--dns=[] : Set custom dns servers for the container
|
||||
--net="bridge" : Set the Network mode for the container
|
||||
--net="bridge" : Connects a container to a network
|
||||
'bridge': creates a new network stack for the container on the docker bridge
|
||||
'none': no networking for this container
|
||||
'container:<name|id>': reuses another container network stack
|
||||
'host': use the host network stack inside the container
|
||||
'NETWORK': connects the container to user-created network using `docker network create` command
|
||||
--add-host="" : Add a line to /etc/hosts (host:IP)
|
||||
--mac-address="" : Sets the container's Ethernet device's MAC address
|
||||
|
||||
@@ -269,12 +270,12 @@ By default, the MAC address is generated using the IP address allocated to the
|
||||
container. You can set the container's MAC address explicitly by providing a
|
||||
MAC address via the `--mac-address` parameter (format:`12:34:56:78:9a:bc`).
|
||||
|
||||
Supported networking modes are:
|
||||
Supported networks :
|
||||
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th class="no-wrap">Mode</th>
|
||||
<th class="no-wrap">Network</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
@@ -304,19 +305,25 @@ Supported networking modes are:
|
||||
its *name* or *id*.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="no-wrap"><strong>NETWORK</strong></td>
|
||||
<td>
|
||||
Connects the container to a user created network (using `docker network create` command)
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
#### Mode: none
|
||||
#### Network: none
|
||||
|
||||
With the networking mode set to `none` a container will not have a
|
||||
With the network is `none` a container will not have
|
||||
access to any external routes. The container will still have a
|
||||
`loopback` interface enabled in the container but it does not have any
|
||||
routes to external traffic.
|
||||
|
||||
#### Mode: bridge
|
||||
#### Network: bridge
|
||||
|
||||
With the networking mode set to `bridge` a container will use docker's
|
||||
With the network set to `bridge` a container will use docker's
|
||||
default networking setup. A bridge is setup on the host, commonly named
|
||||
`docker0`, and a pair of `veth` interfaces will be created for the
|
||||
container. One side of the `veth` pair will remain on the host attached
|
||||
@@ -325,9 +332,9 @@ container's namespaces in addition to the `loopback` interface. An IP
|
||||
address will be allocated for containers on the bridge's network and
|
||||
traffic will be routed though this bridge to the container.
|
||||
|
||||
#### Mode: host
|
||||
#### Network: host
|
||||
|
||||
With the networking mode set to `host` a container will share the host's
|
||||
With the network set to `host` a container will share the host's
|
||||
network stack and all interfaces from the host will be available to the
|
||||
container. The container's hostname will match the hostname on the host
|
||||
system. Note that `--add-host` `--hostname` `--dns` `--dns-search`
|
||||
@@ -343,9 +350,9 @@ or a High Performance Web Server.
|
||||
> **Note**: `--net="host"` gives the container full access to local system
|
||||
> services such as D-bus and is therefore considered insecure.
|
||||
|
||||
#### Mode: container
|
||||
#### Network: container
|
||||
|
||||
With the networking mode set to `container` a container will share the
|
||||
With the network set to `container` a container will share the
|
||||
network stack of another container. The other container's name must be
|
||||
provided in the format of `--net container:<name|id>`. Note that `--add-host`
|
||||
`--hostname` `--dns` `--dns-search` `--dns-opt` and `--mac-address` are
|
||||
@@ -360,6 +367,21 @@ running the `redis-cli` command and connecting to the Redis server over the
|
||||
$ # use the redis container's network stack to access localhost
|
||||
$ docker run --rm -it --net container:redis example/redis-cli -h 127.0.0.1
|
||||
|
||||
#### Network: User-Created NETWORK
|
||||
|
||||
In addition to all the above special networks, user can create a network using
|
||||
their favorite network driver or external plugin. The driver used to create the
|
||||
network takes care of all the network plumbing requirements for the container
|
||||
connected to that network.
|
||||
|
||||
Example creating a network using the inbuilt overlay network driver and running
|
||||
a container in the created network
|
||||
|
||||
```
|
||||
$ docker network create -d overlay multi-host-network
|
||||
$ docker run --net=multi-host-network -itd --name=container3 busybox
|
||||
```
|
||||
|
||||
### Managing /etc/hosts
|
||||
|
||||
Your container will have lines in `/etc/hosts` which define the hostname of the
|
||||
|
||||
@@ -347,7 +347,7 @@ allowing linked communication to continue.
|
||||
# Next step
|
||||
|
||||
Now that you know how to link Docker containers together, the next step is
|
||||
learning how to manage data, volumes and mounts inside your containers.
|
||||
learning how to take complete control over docker networking.
|
||||
|
||||
Go to [Managing Data in Containers](/userguide/dockervolumes).
|
||||
Go to [Docker Networking](/userguide/dockernetworks.md).
|
||||
|
||||
|
||||
@@ -0,0 +1,510 @@
|
||||
<!--[metadata]>
|
||||
+++
|
||||
title = "Docker container networking"
|
||||
description = "How do we connect docker containers within and across hosts ?"
|
||||
keywords = ["Examples, Usage, network, docker, documentation, user guide, multihost, cluster"]
|
||||
[menu.main]
|
||||
parent = "smn_containers"
|
||||
weight = 3
|
||||
+++
|
||||
<![end-metadata]-->
|
||||
|
||||
# Docker container networking
|
||||
|
||||
So far we've been introduced to some [basic Docker
|
||||
concepts](/userguide/usingdocker/), seen how to work with [Docker
|
||||
images](/userguide/dockerimages/) as well as learned about basic [networking
|
||||
and links between containers](/userguide/dockerlinks/). In this section
|
||||
we're going to discuss how you can take control over more advanced
|
||||
container networking.
|
||||
|
||||
This section makes use of `docker network` commands and outputs to explain the
|
||||
advanced networking functionality supported by Docker.
|
||||
|
||||
# Default Networks
|
||||
|
||||
By default, docker creates 3 networks using 3 different network drivers :
|
||||
|
||||
```
|
||||
$ sudo docker network ls
|
||||
NETWORK ID NAME DRIVER
|
||||
7fca4eb8c647 bridge bridge
|
||||
9f904ee27bf5 none null
|
||||
cf03ee007fb4 host host
|
||||
```
|
||||
|
||||
`docker network inspect` gives more information about a network
|
||||
|
||||
```
|
||||
$ sudo docker network inspect bridge
|
||||
{
|
||||
"name": "bridge",
|
||||
"id": "7fca4eb8c647e57e9d46c32714271e0c3f8bf8d17d346629e2820547b2d90039",
|
||||
"driver": "bridge"
|
||||
}
|
||||
```
|
||||
|
||||
By default containers are launched on Bridge network
|
||||
|
||||
```
|
||||
$ sudo docker run -itd --name=container1 busybox
|
||||
f2870c98fd504370fb86e59f32cd0753b1ac9b69b7d80566ffc7192a82b3ed27
|
||||
|
||||
$ sudo docker run -itd --name=container2 busybox
|
||||
bda12f8922785d1f160be70736f26c1e331ab8aaf8ed8d56728508f2e2fd4727
|
||||
```
|
||||
|
||||
```
|
||||
$ sudo docker network inspect bridge
|
||||
{
|
||||
"name": "bridge",
|
||||
"id": "7fca4eb8c647e57e9d46c32714271e0c3f8bf8d17d346629e2820547b2d90039",
|
||||
"driver": "bridge",
|
||||
"containers": {
|
||||
"bda12f8922785d1f160be70736f26c1e331ab8aaf8ed8d56728508f2e2fd4727": {
|
||||
"endpoint": "e0ac95934f803d7e36384a2029b8d1eeb56cb88727aa2e8b7edfeebaa6dfd758",
|
||||
"mac_address": "02:42:ac:11:00:03",
|
||||
"ipv4_address": "172.17.0.3/16"
|
||||
},
|
||||
"f2870c98fd504370fb86e59f32cd0753b1ac9b69b7d80566ffc7192a82b3ed27": {
|
||||
"endpoint": "31de280881d2a774345bbfb1594159ade4ae4024ebfb1320cb74a30225f6a8ae",
|
||||
"mac_address": "02:42:ac:11:00:02",
|
||||
"ipv4_address": "172.17.0.2/16"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
`docker network inspect` command above shows all the connected containers and its network resources on a given network
|
||||
|
||||
Containers in a network should be able to communicate with each other using container names
|
||||
|
||||
```
|
||||
$ sudo docker attach container1
|
||||
|
||||
/ # ifconfig
|
||||
eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:02
|
||||
inet addr:172.17.0.2 Bcast:0.0.0.0 Mask:255.255.0.0
|
||||
inet6 addr: fe80::42:acff:fe11:2/64 Scope:Link
|
||||
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
|
||||
RX packets:17 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:1382 (1.3 KiB) TX bytes:258 (258.0 B)
|
||||
|
||||
lo Link encap:Local Loopback
|
||||
inet addr:127.0.0.1 Mask:255.0.0.0
|
||||
inet6 addr: ::1/128 Scope:Host
|
||||
UP LOOPBACK RUNNING MTU:65536 Metric:1
|
||||
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
|
||||
|
||||
/ # ping container2
|
||||
PING container2 (172.17.0.3): 56 data bytes
|
||||
64 bytes from 172.17.0.3: seq=0 ttl=64 time=0.125 ms
|
||||
64 bytes from 172.17.0.3: seq=1 ttl=64 time=0.130 ms
|
||||
64 bytes from 172.17.0.3: seq=2 ttl=64 time=0.172 ms
|
||||
^C
|
||||
--- container2 ping statistics ---
|
||||
3 packets transmitted, 3 packets received, 0% packet loss
|
||||
round-trip min/avg/max = 0.125/0.142/0.172 ms
|
||||
|
||||
/ # cat /etc/hosts
|
||||
172.17.0.2 f2870c98fd50
|
||||
127.0.0.1 localhost
|
||||
::1 localhost ip6-localhost ip6-loopback
|
||||
fe00::0 ip6-localnet
|
||||
ff00::0 ip6-mcastprefix
|
||||
ff02::1 ip6-allnodes
|
||||
ff02::2 ip6-allrouters
|
||||
172.17.0.2 container1
|
||||
172.17.0.2 container1.bridge
|
||||
172.17.0.3 container2
|
||||
172.17.0.3 container2.bridge
|
||||
```
|
||||
|
||||
|
||||
```
|
||||
$ sudo docker attach container2
|
||||
|
||||
/ # ifconfig
|
||||
eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:03
|
||||
inet addr:172.17.0.3 Bcast:0.0.0.0 Mask:255.255.0.0
|
||||
inet6 addr: fe80::42:acff:fe11:3/64 Scope:Link
|
||||
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
|
||||
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:648 (648.0 B) TX bytes:648 (648.0 B)
|
||||
|
||||
lo Link encap:Local Loopback
|
||||
inet addr:127.0.0.1 Mask:255.0.0.0
|
||||
inet6 addr: ::1/128 Scope:Host
|
||||
UP LOOPBACK RUNNING MTU:65536 Metric:1
|
||||
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
|
||||
|
||||
/ # ping container1
|
||||
PING container1 (172.17.0.2): 56 data bytes
|
||||
64 bytes from 172.17.0.2: seq=0 ttl=64 time=0.277 ms
|
||||
64 bytes from 172.17.0.2: seq=1 ttl=64 time=0.179 ms
|
||||
64 bytes from 172.17.0.2: seq=2 ttl=64 time=0.130 ms
|
||||
64 bytes from 172.17.0.2: seq=3 ttl=64 time=0.113 ms
|
||||
^C
|
||||
--- container1 ping statistics ---
|
||||
4 packets transmitted, 4 packets received, 0% packet loss
|
||||
round-trip min/avg/max = 0.113/0.174/0.277 ms
|
||||
/ # cat /etc/hosts
|
||||
172.17.0.3 bda12f892278
|
||||
127.0.0.1 localhost
|
||||
::1 localhost ip6-localhost ip6-loopback
|
||||
fe00::0 ip6-localnet
|
||||
ff00::0 ip6-mcastprefix
|
||||
ff02::1 ip6-allnodes
|
||||
ff02::2 ip6-allrouters
|
||||
172.17.0.2 container1
|
||||
172.17.0.2 container1.bridge
|
||||
172.17.0.3 container2
|
||||
172.17.0.3 container2.bridge
|
||||
/ #
|
||||
|
||||
```
|
||||
|
||||
# User defined Networks
|
||||
|
||||
In addition to the inbuilt networks, user can create networks using inbuilt drivers
|
||||
(such as bridge or overlay driver) or external plugins supplied by the community.
|
||||
Networks by definition should provides complete isolation for the containers.
|
||||
|
||||
```
|
||||
$ docker network create -d bridge isolated_nw
|
||||
8b05faa32aeb43215f67678084a9c51afbdffe64cd91e3f5bb8267475f8bf1a7
|
||||
|
||||
$ docker network inspect isolated_nw
|
||||
{
|
||||
"name": "isolated_nw",
|
||||
"id": "8b05faa32aeb43215f67678084a9c51afbdffe64cd91e3f5bb8267475f8bf1a7",
|
||||
"driver": "bridge"
|
||||
}
|
||||
|
||||
$ docker network ls
|
||||
NETWORK ID NAME DRIVER
|
||||
9f904ee27bf5 none null
|
||||
cf03ee007fb4 host host
|
||||
7fca4eb8c647 bridge bridge
|
||||
8b05faa32aeb isolated_nw bridge
|
||||
|
||||
```
|
||||
|
||||
Container can be launched on a user-defined network using the --net=<NETWORK> option
|
||||
in `docker run` command
|
||||
|
||||
```
|
||||
$ docker run --net=isolated_nw -itd --name=container3 busybox
|
||||
777344ef4943d34827a3504a802bf15db69327d7abe4af28a05084ca7406f843
|
||||
|
||||
$ docker network inspect isolated_nw
|
||||
{
|
||||
"name": "isolated_nw",
|
||||
"id": "8b05faa32aeb43215f67678084a9c51afbdffe64cd91e3f5bb8267475f8bf1a7",
|
||||
"driver": "bridge",
|
||||
"containers": {
|
||||
"777344ef4943d34827a3504a802bf15db69327d7abe4af28a05084ca7406f843": {
|
||||
"endpoint": "c7f22f8da07fb8ecc687d08377cfcdb80b4dd8624c2a8208b1a4268985e38683",
|
||||
"mac_address": "02:42:ac:14:00:01",
|
||||
"ipv4_address": "172.20.0.1/16"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
# Connecting to Multiple networks
|
||||
|
||||
Docker containers can dynamically connect to 1 or more networks with each network backed
|
||||
by same or different network driver / plugin.
|
||||
|
||||
```
|
||||
$ docker network connect isolated_nw container2
|
||||
$ docker network inspect isolated_nw
|
||||
{
|
||||
"name": "isolated_nw",
|
||||
"id": "8b05faa32aeb43215f67678084a9c51afbdffe64cd91e3f5bb8267475f8bf1a7",
|
||||
"driver": "bridge",
|
||||
"containers": {
|
||||
"777344ef4943d34827a3504a802bf15db69327d7abe4af28a05084ca7406f843": {
|
||||
"endpoint": "c7f22f8da07fb8ecc687d08377cfcdb80b4dd8624c2a8208b1a4268985e38683",
|
||||
"mac_address": "02:42:ac:14:00:01",
|
||||
"ipv4_address": "172.20.0.1/16"
|
||||
},
|
||||
"bda12f8922785d1f160be70736f26c1e331ab8aaf8ed8d56728508f2e2fd4727": {
|
||||
"endpoint": "2ac11345af68b0750341beeda47cc4cce93bb818d8eb25e61638df7a4997cb1b",
|
||||
"mac_address": "02:42:ac:14:00:02",
|
||||
"ipv4_address": "172.20.0.2/16"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Lets check the network resources used by container2.
|
||||
|
||||
```
|
||||
$ docker inspect --format='{{.NetworkSettings.Networks}}' container2
|
||||
[bridge isolated_nw]
|
||||
|
||||
$ sudo docker attach container2
|
||||
|
||||
/ # ifconfig
|
||||
eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:03
|
||||
inet addr:172.17.0.3 Bcast:0.0.0.0 Mask:255.255.0.0
|
||||
inet6 addr: fe80::42:acff:fe11:3/64 Scope:Link
|
||||
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
|
||||
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:1586 (1.5 KiB) TX bytes:1460 (1.4 KiB)
|
||||
|
||||
eth1 Link encap:Ethernet HWaddr 02:42:AC:14:00:02
|
||||
inet addr:172.20.0.2 Bcast:0.0.0.0 Mask:255.255.0.0
|
||||
inet6 addr: fe80::42:acff:fe14:2/64 Scope:Link
|
||||
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
|
||||
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:648 (648.0 B) TX bytes:648 (648.0 B)
|
||||
|
||||
lo Link encap:Local Loopback
|
||||
inet addr:127.0.0.1 Mask:255.0.0.0
|
||||
inet6 addr: ::1/128 Scope:Host
|
||||
UP LOOPBACK RUNNING MTU:65536 Metric:1
|
||||
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
|
||||
```
|
||||
|
||||
|
||||
In the example discussed in this section thus far, container3 and container2 are
|
||||
connected to isolated_nw and can talk to each other.
|
||||
But container3 and container1 are not in the same network and hence they cannot communicate.
|
||||
|
||||
```
|
||||
$ docker attach container3
|
||||
|
||||
/ # ifconfig
|
||||
eth0 Link encap:Ethernet HWaddr 02:42:AC:14:00:01
|
||||
inet addr:172.20.0.1 Bcast:0.0.0.0 Mask:255.255.0.0
|
||||
inet6 addr: fe80::42:acff:fe14:1/64 Scope:Link
|
||||
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
|
||||
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:1944 (1.8 KiB) TX bytes:648 (648.0 B)
|
||||
|
||||
lo Link encap:Local Loopback
|
||||
inet addr:127.0.0.1 Mask:255.0.0.0
|
||||
inet6 addr: ::1/128 Scope:Host
|
||||
UP LOOPBACK RUNNING MTU:65536 Metric:1
|
||||
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
|
||||
|
||||
/ # ping container2.isolated_nw
|
||||
PING container2.isolated_nw (172.20.0.2): 56 data bytes
|
||||
64 bytes from 172.20.0.2: seq=0 ttl=64 time=0.217 ms
|
||||
64 bytes from 172.20.0.2: seq=1 ttl=64 time=0.150 ms
|
||||
64 bytes from 172.20.0.2: seq=2 ttl=64 time=0.188 ms
|
||||
64 bytes from 172.20.0.2: seq=3 ttl=64 time=0.176 ms
|
||||
^C
|
||||
--- container2.isolated_nw ping statistics ---
|
||||
4 packets transmitted, 4 packets received, 0% packet loss
|
||||
round-trip min/avg/max = 0.150/0.182/0.217 ms
|
||||
/ # ping container2
|
||||
PING container2 (172.20.0.2): 56 data bytes
|
||||
64 bytes from 172.20.0.2: seq=0 ttl=64 time=0.120 ms
|
||||
64 bytes from 172.20.0.2: seq=1 ttl=64 time=0.109 ms
|
||||
^C
|
||||
--- container2 ping statistics ---
|
||||
2 packets transmitted, 2 packets received, 0% packet loss
|
||||
round-trip min/avg/max = 0.109/0.114/0.120 ms
|
||||
|
||||
/ # ping container1
|
||||
ping: bad address 'container1'
|
||||
|
||||
/ # ping 172.17.0.2
|
||||
PING 172.17.0.2 (172.17.0.2): 56 data bytes
|
||||
^C
|
||||
--- 172.17.0.2 ping statistics ---
|
||||
4 packets transmitted, 0 packets received, 100% packet loss
|
||||
|
||||
/ # ping 172.17.0.3
|
||||
PING 172.17.0.3 (172.17.0.3): 56 data bytes
|
||||
^C
|
||||
--- 172.17.0.3 ping statistics ---
|
||||
4 packets transmitted, 0 packets received, 100% packet loss
|
||||
|
||||
```
|
||||
|
||||
While container2 is attached to both the networks (bridge and isolated_nw) and hence it
|
||||
can talk to both container1 and container3
|
||||
|
||||
```
|
||||
$ docker attach container2
|
||||
|
||||
/ # cat /etc/hosts
|
||||
172.17.0.3 bda12f892278
|
||||
127.0.0.1 localhost
|
||||
::1 localhost ip6-localhost ip6-loopback
|
||||
fe00::0 ip6-localnet
|
||||
ff00::0 ip6-mcastprefix
|
||||
ff02::1 ip6-allnodes
|
||||
ff02::2 ip6-allrouters
|
||||
172.17.0.2 container1
|
||||
172.17.0.2 container1.bridge
|
||||
172.17.0.3 container2
|
||||
172.17.0.3 container2.bridge
|
||||
172.20.0.1 container3
|
||||
172.20.0.1 container3.isolated_nw
|
||||
172.20.0.2 container2
|
||||
172.20.0.2 container2.isolated_nw
|
||||
|
||||
/ # ping container3
|
||||
PING container3 (172.20.0.1): 56 data bytes
|
||||
64 bytes from 172.20.0.1: seq=0 ttl=64 time=0.138 ms
|
||||
64 bytes from 172.20.0.1: seq=1 ttl=64 time=0.133 ms
|
||||
64 bytes from 172.20.0.1: seq=2 ttl=64 time=0.133 ms
|
||||
^C
|
||||
--- container3 ping statistics ---
|
||||
3 packets transmitted, 3 packets received, 0% packet loss
|
||||
round-trip min/avg/max = 0.133/0.134/0.138 ms
|
||||
|
||||
/ # ping container1
|
||||
PING container1 (172.17.0.2): 56 data bytes
|
||||
64 bytes from 172.17.0.2: seq=0 ttl=64 time=0.121 ms
|
||||
64 bytes from 172.17.0.2: seq=1 ttl=64 time=0.250 ms
|
||||
64 bytes from 172.17.0.2: seq=2 ttl=64 time=0.133 ms
|
||||
^C
|
||||
--- container1 ping statistics ---
|
||||
3 packets transmitted, 3 packets received, 0% packet loss
|
||||
round-trip min/avg/max = 0.121/0.168/0.250 ms
|
||||
/ #
|
||||
```
|
||||
|
||||
|
||||
Just like it is easy to connect a container to multiple networks, one can
|
||||
disconnect a container from a network using the `docker network disconnect` command.
|
||||
|
||||
```
|
||||
root@Ubuntu-vm ~$ docker network disconnect isolated_nw container2
|
||||
|
||||
$ docker inspect --format='{{.NetworkSettings.Networks}}' container2
|
||||
[bridge]
|
||||
|
||||
root@Ubuntu-vm ~$ docker network inspect isolated_nw
|
||||
{
|
||||
"name": "isolated_nw",
|
||||
"id": "8b05faa32aeb43215f67678084a9c51afbdffe64cd91e3f5bb8267475f8bf1a7",
|
||||
"driver": "bridge",
|
||||
"containers": {
|
||||
"777344ef4943d34827a3504a802bf15db69327d7abe4af28a05084ca7406f843": {
|
||||
"endpoint": "c7f22f8da07fb8ecc687d08377cfcdb80b4dd8624c2a8208b1a4268985e38683",
|
||||
"mac_address": "02:42:ac:14:00:01",
|
||||
"ipv4_address": "172.20.0.1/16"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Once a container is disconnected from a network, it cannot communicate with other containers
|
||||
connected to that network. In this example, container2 cannot talk to container3 any more
|
||||
in isolated_nw
|
||||
|
||||
```
|
||||
$ sudo docker attach container2
|
||||
|
||||
/ # ifconfig
|
||||
eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:03
|
||||
inet addr:172.17.0.3 Bcast:0.0.0.0 Mask:255.255.0.0
|
||||
inet6 addr: fe80::42:acff:fe11:3/64 Scope:Link
|
||||
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
|
||||
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:1964 (1.9 KiB) TX bytes:1838 (1.7 KiB)
|
||||
|
||||
lo Link encap:Local Loopback
|
||||
inet addr:127.0.0.1 Mask:255.0.0.0
|
||||
inet6 addr: ::1/128 Scope:Host
|
||||
UP LOOPBACK RUNNING MTU:65536 Metric:1
|
||||
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
|
||||
|
||||
/ # ping container3
|
||||
PING container3 (172.20.0.1): 56 data bytes
|
||||
^C
|
||||
--- container3 ping statistics ---
|
||||
2 packets transmitted, 0 packets received, 100% packet loss
|
||||
|
||||
|
||||
But container2 still has full connectivity to the bridge network
|
||||
|
||||
/ # ping container1
|
||||
PING container1 (172.17.0.2): 56 data bytes
|
||||
64 bytes from 172.17.0.2: seq=0 ttl=64 time=0.119 ms
|
||||
64 bytes from 172.17.0.2: seq=1 ttl=64 time=0.174 ms
|
||||
^C
|
||||
--- container1 ping statistics ---
|
||||
2 packets transmitted, 2 packets received, 0% packet loss
|
||||
round-trip min/avg/max = 0.119/0.146/0.174 ms
|
||||
/ #
|
||||
|
||||
```
|
||||
|
||||
When all the containers in a network stops or disconnected the network can be removed
|
||||
|
||||
```
|
||||
$ docker network inspect isolated_nw
|
||||
{
|
||||
"name": "isolated_nw",
|
||||
"id": "8b05faa32aeb43215f67678084a9c51afbdffe64cd91e3f5bb8267475f8bf1a7",
|
||||
"driver": "bridge"
|
||||
}
|
||||
|
||||
$ docker network rm isolated_nw
|
||||
|
||||
$ docker network ls
|
||||
NETWORK ID NAME DRIVER
|
||||
9f904ee27bf5 none null
|
||||
cf03ee007fb4 host host
|
||||
7fca4eb8c647 bridge bridge
|
||||
```
|
||||
|
||||
# Native Multi-host networking
|
||||
|
||||
With the help of libnetwork and the inbuilt `VXLAN based overlay network driver` docker supports multi-host networking natively out of the box. Technical details are documented under https://github.com/docker/libnetwork/blob/master/docs/overlay.md.
|
||||
Using the exact same above `docker network` UI, the user can exercise the power of multi-host networking.
|
||||
|
||||
In order to create a network using the inbuilt overlay driver,
|
||||
|
||||
```
|
||||
$ docker network create -d overlay multi-host-network
|
||||
```
|
||||
|
||||
Since `network` object is globally significant, this feature requires distributed states provided by `libkv`. Using `libkv`, the user can plug any of the supported Key-Value store (such as consul, etcd or zookeeper).
|
||||
User can specify the Key-Value store of choice using the `--cluster-store` daemon flag, which takes configuration value of format `PROVIDER://URL`, where
|
||||
`PROVIDER` is the name of the Key-Value store (such as consul, etcd or zookeeper) and
|
||||
`URL` is the url to reach the Key-Value store.
|
||||
Example : `docker daemon --cluster-store=consul://localhost:8500`
|
||||
|
||||
# Next step
|
||||
|
||||
Now that you know how to link Docker containers together, the next step is
|
||||
learning how to manage data, volumes and mounts inside your containers.
|
||||
|
||||
Go to [Managing Data in Containers](/userguide/dockervolumes.md).
|
||||
+16
-6
@@ -42,7 +42,7 @@ Go to [Using Docker Hub](/docker-hub).
|
||||
Docker offers a *container-based* virtualization platform to power your
|
||||
applications. To learn how to Dockerize applications and run them:
|
||||
|
||||
Go to [Dockerizing Applications](/userguide/dockerizing).
|
||||
Go to [Dockerizing Applications](/docs/userguide/dockerizing.md).
|
||||
|
||||
## Working with containers
|
||||
|
||||
@@ -52,7 +52,7 @@ Once you get a grip on running your applications in Docker containers
|
||||
we're going to show you how to manage those containers. To find out
|
||||
about how to inspect, monitor and manage containers:
|
||||
|
||||
Go to [Working With Containers](/userguide/usingdocker).
|
||||
Go to [Working With Containers](/docs/userguide/usingdocker.md).
|
||||
|
||||
## Working with Docker images
|
||||
|
||||
@@ -61,7 +61,7 @@ Go to [Working With Containers](/userguide/usingdocker).
|
||||
Once you've learnt how to use Docker it's time to take the next step and
|
||||
learn how to build your own application images with Docker.
|
||||
|
||||
Go to [Working with Docker Images](/userguide/dockerimages).
|
||||
Go to [Working with Docker Images](/docs/userguide/dockerimages.md).
|
||||
|
||||
## Linking containers together
|
||||
|
||||
@@ -69,14 +69,24 @@ Until now we've seen how to build individual applications inside Docker
|
||||
containers. Now learn how to build whole application stacks with Docker
|
||||
by linking together multiple Docker containers.
|
||||
|
||||
Go to [Linking Containers Together](/userguide/dockerlinks).
|
||||
Go to [Linking Containers Together](/docs/userguide/dockerlinks.md).
|
||||
|
||||
## Docker container networking
|
||||
|
||||
Links provides a very easy and convenient way to connect the containers.
|
||||
But, it is very opinionated and doesnt provide a lot of flexibility or
|
||||
choice to the end-users. Now, lets learn about a flexible way to connect
|
||||
containers together within a host or across multiple hosts in a cluster
|
||||
using various networking technologies, with the help of extensible plugins.
|
||||
|
||||
Go to [Docker Networking](/docs/userguide/dockernetworks.md).
|
||||
|
||||
## Managing data in containers
|
||||
|
||||
Now we know how to link Docker containers together the next step is
|
||||
learning how to manage data, volumes and mounts inside our containers.
|
||||
|
||||
Go to [Managing Data in Containers](/userguide/dockervolumes).
|
||||
Go to [Managing Data in Containers](/docs/userguide/dockervolumes.md).
|
||||
|
||||
## Working with Docker Hub
|
||||
|
||||
@@ -84,7 +94,7 @@ Now we've learned a bit more about how to use Docker we're going to see
|
||||
how to combine Docker with the services available on Docker Hub including
|
||||
Trusted Builds and private repositories.
|
||||
|
||||
Go to [Working with Docker Hub](/userguide/dockerrepos).
|
||||
Go to [Working with Docker Hub](/docs/userguide/dockerrepos.md).
|
||||
|
||||
## Docker Compose
|
||||
|
||||
|
||||
Reference in New Issue
Block a user