Files
cli/components/engine/daemon
Madhu Venugopal 058521db69 Adding container to secondary network to support port mapping
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
2015-06-22 04:15:57 -07:00
..
2015-06-16 15:19:43 -07:00
2015-06-10 20:21:50 +02:00
2015-05-14 15:57:45 -07:00
2015-06-19 15:29:47 -07:00
2015-06-12 09:21:17 -07:00
2015-06-01 12:39:28 -07:00
2015-06-01 12:39:28 -07:00
2015-06-01 12:39:28 -07:00
2015-06-01 12:39:28 -07:00
2015-06-01 12:39:28 -07:00
2015-06-01 12:39:28 -07:00
2015-06-15 18:18:38 -04:00
2015-06-01 12:39:28 -07:00
2015-06-01 12:39:28 -07:00
2015-06-01 12:39:28 -07:00
2015-05-29 22:38:09 +02:00

This directory contains code pertaining to running containers and storing images

Code pertaining to running containers:

  • execdriver
  • networkdriver

Code pertaining to storing images:

  • graphdriver