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

Add network interal mode 

Signed-off-by: Chun Chen <ramichen@tencent.com>
Signed-off-by: David Calavera <david.calavera@gmail.com>
This commit is contained in:
Chun Chen 2015-12-28 10:15:50 +08:00 committed by Tibor Vass
parent 9c8b6e05a4
commit 3f5817fdae
2 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/reference/commandline/network_create.md
View File

@ -18,6 +18,7 @@ parent = "smn_cli"
-d --driver=DRIVER Driver to manage the Network bridge or overlay. The default is bridge. -d --driver=DRIVER Driver to manage the Network bridge or overlay. The default is bridge.
--gateway=[] ipv4 or ipv6 Gateway for the master subnet --gateway=[] ipv4 or ipv6 Gateway for the master subnet
--help Print usage --help Print usage
--internal Restricts external access to the network
--ip-range=[] Allocate container ip from a sub-range --ip-range=[] Allocate container ip from a sub-range
--ipam-driver=default IP Address Management Driver --ipam-driver=default IP Address Management Driver
-o --opt=map[] Set custom network plugin options -o --opt=map[] Set custom network plugin options
@ -120,6 +121,11 @@ docker network create -d overlay
``` ```
Be sure that your subnetworks do not overlap. If they do, the network create fails and Engine returns an error. Be sure that your subnetworks do not overlap. If they do, the network create fails and Engine returns an error.
### Network internal mode
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 to create an externally isolated `overlay` network, you can specify the `--internal` option.
## Related information ## Related information
* [network inspect](network_inspect.md) * [network inspect](network_inspect.md)

9
man/docker-network-create.1.md
View File

@ -10,6 +10,7 @@ docker-network-create - create a new network
[**-d**|**--driver**=*DRIVER*] [**-d**|**--driver**=*DRIVER*]
[**--gateway**=*[]*] [**--gateway**=*[]*]
[**--help**] [**--help**]
[**--internal**]
[**--ip-range**=*[]*] [**--ip-range**=*[]*]
[**--ipam-driver**=*default*] [**--ipam-driver**=*default*]
[**-o**|**--opt**=*map[]*] [**-o**|**--opt**=*map[]*]
@ -120,6 +121,11 @@ docker network create -d overlay
``` ```
Be sure that your subnetworks do not overlap. If they do, the network create fails and Engine returns an error. Be sure that your subnetworks do not overlap. If they do, the network create fails and Engine returns an error.
### Network internal mode
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 to create an externally isolated `overlay` network, you can specify the `--internal` option.
# OPTIONS # OPTIONS
**--aux-address**=map[] **--aux-address**=map[]
Auxiliary ipv4 or ipv6 addresses used by network driver Auxiliary ipv4 or ipv6 addresses used by network driver
@ -133,6 +139,9 @@ Be sure that your subnetworks do not overlap. If they do, the network create fai
**--help** **--help**
Print usage Print usage
**--internal**
Restricts external access to the network
**--ip-range**=[] **--ip-range**=[]
Allocate container ip from a sub-range Allocate container ip from a sub-range