jyapayne/compose
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add support for creating internal networks

Browse source 
Signed-off-by: Jonathan Giannuzzi <jonathan@giannuzzi.be>
This commit is contained in:
Jonathan Giannuzzi 2016-07-11 11:34:01 +02:00
commit 83f35e132b
7 changed files with 77 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/compose-file.md
View file

@ -859,6 +859,10 @@ A full example:
host2: 172.28.1.6
host3: 172.28.1.7
### internal
By default, Docker also connects a bridge network to it to provide external connectivity. If you want to create an externally isolated overlay network, you can set this option to `true`.
### external
If set to `true`, specifies that this network has been created outside of
@ -866,7 +870,7 @@ Compose. `docker-compose up` will not attempt to create it, and will raise
an error if it doesn't exist.
`external` cannot be used in conjunction with other network configuration keys
(`driver`, `driver_opts`, `ipam`).
(`driver`, `driver_opts`, `ipam`, `internal`).
In the example below, `proxy` is the gateway to the outside world. Instead of
attemping to create a network called `[projectname]_outside`, Compose will