Madhu Venugopal aeae6b501d Reading the top level element (network) from datastore on init ...

Currently we rely on watch to catchup after the init. But there could be
a small time window on which, we might end up in a race condition on
network creates. By reading and populating networks during init, we
avoid any such conditions, especially for default network handling.

Signed-off-by: Madhu Venugopal <madhu@docker.com>

2015-06-18 08:35:46 -07:00

..

dnet_test.go

Initial dnet tool to test and manage libnetwork end-to-end

2015-05-19 14:10:30 -07:00

dnet.go

Updating CallFunc to match the Docker CLI API changes

2015-06-15 09:41:28 -07:00

flags.go

Moved the TOML based Configuration to dnet

2015-06-12 12:46:12 -07:00

libnetwork.toml

Reading the top level element (network) from datastore on init

2015-06-18 08:35:46 -07:00