Alessandro Boch 9f01da606a Support configuration networks ...

- They are configuration-only networks which
  can be used to supply the configuration
  when creating regular networks.
- They do not get allocated and do net get plumbed.
  Drivers do not get to know about them.
- They can be removed, once no other network is
  using them.
- When user creates a network specifying a
  configuration network for the config, no
  other network specific configuration field
  is are accepted. User can only specify
  network operator fields (attachable, internal,...)

Signed-off-by: Alessandro Boch <aboch@docker.com>
Upstream-commit: 9ee7b4dda926a1444dc0ea50c4ca6d90c8684060
Component: engine

2017-05-17 15:50:28 -07:00

..

build

Add docker build --iidfile=FILE

2017-05-05 16:35:54 +01:00

checkpoint

Use function arguments for route setup.

2017-04-12 08:43:51 -04:00

container

Update ContainerWait API

2017-05-16 15:11:39 -07:00

distribution

api: Use OCI types for Digest and Platform

2017-05-16 14:54:23 -07:00

image

Refacator pkg/streamformatter

2017-05-02 17:38:12 -04:00

network

Support configuration networks

2017-05-17 15:50:28 -07:00

plugin

Refacator pkg/streamformatter

2017-05-02 17:38:12 -04:00

swarm

Disabling digest pinning for API versions < 1.30

2017-05-15 16:42:43 -07:00

system

Honor context within SystemDiskUsage

2017-04-24 09:11:29 -07:00

volume

Honor context cancellation when pruning

2017-04-24 09:11:29 -07:00

experimental.go

router: Return explicit error rather than 404 for experimental.

2016-11-17 15:51:47 -08:00

local.go

Use function arguments for route setup.

2017-04-12 08:43:51 -04:00

router.go

Decouple the "container" router from the actual daemon implementation.

2016-02-08 11:30:57 -05:00