Allow user to modify ingress network

Signed-off-by: Alessandro Boch <aboch@docker.com>
This commit is contained in:
Alessandro Boch 2017-03-09 11:52:25 -08:00 committed by Tibor Vass
parent a10f63f0ce
commit bf7ba6964b
3 changed files with 37 additions and 0 deletions

View File

@ -22,6 +22,7 @@ Create a network
Options: Options:
--attachable Enable manual container attachment --attachable Enable manual container attachment
--ingress Specify the network provides the routing-mesh
--aux-address value Auxiliary IPv4 or IPv6 addresses used by Network --aux-address value Auxiliary IPv4 or IPv6 addresses used by Network
driver (default map[]) driver (default map[])
-d, --driver string Driver to manage the Network (default "bridge") -d, --driver string Driver to manage the Network (default "bridge")
@ -195,6 +196,23 @@ connects a bridge network to it to provide external connectivity. If you want
to create an externally isolated `overlay` network, you can specify the to create an externally isolated `overlay` network, you can specify the
`--internal` option. `--internal` option.
### Network ingress mode
You can create the network which will be used to provide the routing-mesh in the
swarm cluster. You do so by specifying `--ingress` when creating the network. Only
one ingress network can be created at the time. The network can be removed only
if no services depend on it. Any option available when creating a overlay network
is also available when creating the ingress network, besides the `--attachable` option.
```bash
$ docker network create -d overlay \
--subnet=10.11.0.0/16 \
--ingress \
--opt com.docker.network.mtu=9216 \
--opt encrypted=true \
my-ingress-network
```
## Related commands ## Related commands
* [network inspect](network_inspect.md) * [network inspect](network_inspect.md)

View File

@ -117,3 +117,20 @@ By default, when you connect a container to an `overlay` network, Docker also
connects a bridge network to it to provide external connectivity. If you want connects a bridge network to it to provide external connectivity. If you want
to create an externally isolated `overlay` network, you can specify the to create an externally isolated `overlay` network, you can specify the
`--internal` option. `--internal` option.
### Network ingress mode
You can create the network which will be used to provide the routing-mesh in the
swarm cluster. You do so by specifying `--ingress` when creating the network. Only
one ingress network can be created at the time. The network can be removed only
if no services depend on it. Any option available when creating a overlay network
is also available when creating the ingress network, besides the `--attachable` option.
```bash
$ docker network create -d overlay \
--subnet=10.11.0.0/16 \
--ingress \
--opt com.docker.network.mtu=9216 \
--opt encrypted=true \
my-ingress-network
```

View File

@ -32,6 +32,7 @@ $ sudo docker network inspect bridge
] ]
}, },
"Internal": false, "Internal": false,
"Ingress": false,
"Containers": { "Containers": {
"bda12f8922785d1f160be70736f26c1e331ab8aaf8ed8d56728508f2e2fd4727": { "bda12f8922785d1f160be70736f26c1e331ab8aaf8ed8d56728508f2e2fd4727": {
"Name": "container2", "Name": "container2",
@ -116,6 +117,7 @@ $ docker network inspect --verbose ov1
}, },
"Internal": false, "Internal": false,
"Attachable": false, "Attachable": false,
"Ingress": false,
"Containers": { "Containers": {
"020403bd88a15f60747fd25d1ad5fa1272eb740e8a97fc547d8ad07b2f721c5e": { "020403bd88a15f60747fd25d1ad5fa1272eb740e8a97fc547d8ad07b2f721c5e": {
"Name": "s1.1.pjn2ik0sfgkfzed3h0s00gs9o", "Name": "s1.1.pjn2ik0sfgkfzed3h0s00gs9o",