058521db69cfaad0e48648d5d17905fd29a2584e
With publish-service and default-network support, a container could be connected to a user-defined network that is backed by any driver/plugin. But if the user uses port mapping or expose commands, the expectation for that container is to behave like existing bridge network. Thanks to the Libnetwork's CNM model, containers can be connected to the bridge network as a secondary network in addition to the user-specified network. Signed-off-by: Madhu Venugopal <madhu@docker.com> Upstream-commit: 739996c1d78976f7435c7274300b3e8f2e598b17 Component: engine
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%