Files
docker-cli/components/engine/pkg
Brian Goff f0e82098a7 Add back compat for volume drivers Get and Ls
Use a back-compat struct to handle listing volumes for volumes we know
about (because, presumably, they are being used by a container) for
volume drivers which don't yet support `List`.

Adds a fall-back for the volume driver `Get` call, which will use
`Create` when the driver returns a `404` for `Get`. The old behavior was
to always use `Create` to get a volume reference.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
Upstream-commit: f6c20d9b22ec9913f67b6c2ebdb5ef07c87b8cd7
Component: engine
2016-01-22 22:48:17 -05:00
..
2015-12-13 18:04:12 +02:00
2015-07-16 16:02:26 -07:00
2015-09-09 14:59:25 +02:00
2015-12-22 15:17:15 -05:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-12-22 14:15:07 -05:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-12-02 16:43:49 -05:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-12-22 13:31:43 -05:00
2015-12-31 13:07:35 +00:00
2015-12-13 18:04:12 +02:00
2015-11-02 08:02:25 -08:00
2015-07-27 21:26:21 +02:00
2015-12-17 11:52:23 +01:00
2013-12-23 23:12:19 +00:00

pkg/ is a collection of utility packages used by the Docker project without being specific to its internals.

Utility packages are kept separate from the docker core codebase to keep it as small and concise as possible. If some utilities grow larger and their APIs stabilize, they may be moved to their own repository under the Docker organization, to facilitate re-use by other projects. However that is not the priority.

The directory pkg is named after the same directory in the camlistore project. Since Brad is a core Go maintainer, we thought it made sense to copy his methods for organizing Go code :) Thanks Brad!

Because utility packages are small and neatly separated from the rest of the codebase, they are a good place to start for aspiring maintainers and contributors. Get in touch if you want to help maintain them!