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

..

backend/build

Extract squash and tagging from the Dockerfile builder.

2017-05-01 12:07:32 -04:00

httputils

Change log details encoding format and support details on service logs

2017-05-12 10:53:44 -07:00

middleware

Hide command options that are related to Windows

2017-03-12 08:47:17 +02:00

router

Support configuration networks

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

middleware.go

change comment

2016-08-26 18:30:41 +08:00

profiler.go

Use generic handler for pprof profile lookups

2017-03-16 11:05:20 -04:00

router_swapper.go

fix typos

2016-03-06 00:59:11 +08:00

server_test.go

Correct fmt.Fprintf and t.Fatalf

2017-02-08 12:32:40 +08:00

server.go

server.go: format for

2017-05-15 07:12:28 +08:00