Files
docker-cli/components/engine/pkg
Phil Estes 9aebf5450b Correct build-time directory creation with user namespaced daemon
This fixes errors in ownership on directory creation during build that
can cause inaccessible files depending on the paths in the Dockerfile
and non-existing directories in the starting image.

Add tests for the mkdir variants in pkg/idtools

Docker-DCO-1.1-Signed-off-by: Phil Estes <estesp@linux.vnet.ibm.com> (github: estesp)
Upstream-commit: ae8c004dc18c59fec9cd67759a5e0087300e872d
Component: engine
2015-10-20 08:59:48 -04:00
..
2015-09-18 13:39:12 -07:00
2015-07-16 16:02:26 -07:00
2015-09-09 14:59:25 +02:00
2015-06-17 01:16:57 +03:00
2015-07-22 10:26:10 +02:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-07-29 21:25:56 +03:00
2015-10-13 08:42:47 -07:00
2015-07-29 21:25:56 +03:00
2015-07-27 21:26:21 +02:00
2015-08-25 16:50:08 -04:00
2015-09-15 22:20:10 +02:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-03-25 00:46:22 +08: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!