Madhu Venugopal 521162c904 fixed incorrect assumption on --bridge=none treated as disable network ...

libnetwork host, none and bridge driver initialization is incorrectly
disabled if the daemon flag --bridge=none. The expected behavior of
setting --bridge as none is to disable the bridge driver alone and let
all other modes to be operational.

Signed-off-by: Madhu Venugopal <madhu@docker.com>
Upstream-commit: c9328c6ccf120abda297d11fcfc7e60c7c31ec21
Component: engine

2015-06-30 13:04:28 -07:00

components/engine

fixed incorrect assumption on --bridge=none treated as disable network

2015-06-30 13:04:28 -07:00

Description

No description provided

310 MiB

Languages

Go 92%

Shell 5.5%

Dockerfile 1.1%

Go-Checksums 0.9%

Makefile 0.3%

Other 0.2%