Files
docker-cli/components/engine/pkg
Antonio Murdaca 0bc559ba8a pkg: chrootarchive: chroot_linux: fix docker build
The path we're trying to remove doesn't exist after a successful
chroot+chdir because a / is only appended after pivot_root is
successful and so we can't cleanup anymore with the old path.
Also fix leaking .pivot_root dirs under /var/lib/docker/tmp/docker-builder*
on error.

Fix https://github.com/docker/docker/issues/22587
Introduced by https://github.com/docker/docker/pull/22506

Signed-off-by: Antonio Murdaca <runcom@redhat.com>
Upstream-commit: 5248f5c3d1d91ea4235ffe57962e38293af18f34
Component: engine
2016-05-10 00:42:49 +02:00
..
2016-05-06 18:23:11 +08:00
2016-05-06 18:23:11 +08:00
2016-05-06 18:23:11 +08:00
2016-03-21 22:03:24 -07:00
2016-04-09 21:18:15 +08:00
2016-04-09 21:18:15 +08:00
2016-04-09 21:18:15 +08:00
2016-04-09 21:18:15 +08:00
2016-03-25 22:14:27 -04:00
2016-04-09 21:18:15 +08:00
2016-04-09 21:18:15 +08:00
2016-03-08 07:55:01 -08:00
2016-04-09 21:18:15 +08:00
2016-04-25 15:57:59 -07: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!