Files
docker-cli/components/engine/pkg
Dan Walsh 47e00eae65 No options to tmpfs is valid
If you run a

docker run command with --tmpfs /mountpoint:noexec

Or certain options that get translated into mount options, the mount command can get passed "" for mount data.
So this should be valid.

Signed-off-by: Dan Walsh <dwalsh@redhat.com>
Upstream-commit: 89a775d2dc596b9ac86873edf447fff2f7012ef3
Component: engine
2015-12-22 14:15:07 -05:00
..
2015-12-13 18:04:12 +02:00
2015-12-18 16:29:01 +01:00
2015-07-16 16:02:26 -07:00
2015-09-09 14:59:25 +02:00
2015-12-13 18:04:12 +02: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-12-18 16:29:01 +01: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-13 18:04:12 +02:00
2015-12-13 18:04:12 +02: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-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!