5ce830016b
Often it happens that docker is not able to shutdown/remove the thin pool it created because some device has leaked into some mount name space. That means device is in use and that means pool can't be removed. Docker will leave pool as it is and exit. Later when user starts the docker, it finds pool is already there and docker uses it. But docker does not know it is same pool which is using the loop devices. Now docker thinks loop devices are not being used. That means it does not display the data correctly in "docker info", giving user wrong information. This patch tries to detect if loop devices as created by docker are being used for pool and fills in the right details in "docker info". Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Upstream-commit: bebf53443981c70a6a714ea518dc966a0e2b6558 Component: engine
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!