Files
docker-cli/components/engine/pkg
Brian Goff 55cea3f58e idtools don't chown if not needed
In some cases (e.g. NFS), a chown may technically be a no-op but still
return `EPERM`, so only call `chown` when neccessary.

This is particularly problematic for docker users bind-mounting an NFS
share into a container.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
Upstream-commit: fa9709a3fc51785c3dc0f7ca8f54dafde2e291ab
Component: engine
2017-10-19 16:06:25 -04:00
..
2017-09-12 12:09:59 -04:00
2017-08-24 15:08:31 -04:00
2017-09-12 12:09:59 -04:00
2017-07-31 13:16:46 -07:00
2017-08-21 18:15:08 -04:00
2017-10-19 16:06:25 -04:00
2017-08-18 14:23:44 -04:00
2017-09-10 11:34:19 +02:00
2017-09-12 12:09:59 -04:00
2017-05-08 17:02:02 -07:00
2017-07-31 13:16:46 -07:00
2017-07-31 13:16:46 -07:00
2017-09-08 18:23:21 -04:00
2017-09-12 12:09:59 -04:00
2017-09-12 12:09:59 -04:00
2017-07-03 13:13:09 -07:00
2017-08-21 18:15:08 -04:00
2017-05-08 17:02:02 -07:00
2017-05-08 17:02:02 -07:00
2017-07-31 13:16:46 -07:00
2017-09-14 13:51:16 -07:00
2016-11-13 20:08:51 -08:00
2017-09-08 18:23:21 -04:00
2017-09-08 18:23:21 -04:00
2017-06-26 10:07:04 -07: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!