Remove ability to join bridge network + user-defined networks

Containers connected to the bridge network can't have aliases, so it's
simpler to rule that they can *either* be connected to the bridge
network (via `network_mode: bridge`) *or* be connected to user-defined
networks (via `networks` or the default network).

Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
This commit is contained in:
Aanand Prasad 2016-01-27 00:42:04 +00:00
commit 297d20f085
3 changed files with 6 additions and 30 deletions

View file

@ -472,11 +472,6 @@ Networks to join, referencing entries under the
- some-network
- other-network
The value `bridge` can also be used to make containers join the pre-defined
`bridge` network.
There is no equivalent to `net: "container:[name or id]"`.
### pid
pid: "host"