Files
docker-cli/components/engine/pkg
Serge Hallyn cc5b6aa3dd Don't create devices if in a user namespace
If we are running in a user namespace, don't try to mknod as
it won't be allowed.  libcontainer will bind-mount the host's
devices over files in the container anyway, so it's not needed.

The chrootarchive package does a chroot (without mounting /proc) before
its work, so we cannot check /proc/self/uid_map when we need to.  So
compute it in advance and pass it along with the tar options.

Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
Upstream-commit: 617c352e9225b1d598e893aa5f89a8863808e4f2
Component: engine
2016-08-12 16:26:58 -04:00
..
2016-07-23 11:32:23 +08:00
2016-06-02 17:17:22 +08:00
2016-06-02 17:17:22 +08:00
2015-12-13 18:04:12 +02:00
2016-06-11 13:16:55 -07:00
2016-05-26 19:28:18 -07:00
2016-08-01 22:01:20 +08:00
2016-07-26 08:53:54 +00:00
2016-06-23 16:09:13 -07:00
2016-06-02 17:17:22 +08:00
2015-12-13 18:04:12 +02:00
2016-08-10 22:56:05 +08:00
2016-04-09 21:18:15 +08:00
2016-07-21 20:04:47 -07:00
2016-03-25 22:14:27 -04:00
2016-08-10 22:56:05 +08:00
2016-08-10 22:56:05 +08:00
2016-08-10 22:56:05 +08:00
2015-11-02 08:02:25 -08:00
2016-04-28 11:04:50 +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!