c94111b619
Such nodes could already be created by importing a tarball to a container; now they can be created from within the container itself. This gives non-privileged containers the mknod kernel capability, and modifies their cgroup settings to allow creation of *any* node, not just whitelisted ones. Use of such nodes is still controlled by the existing cgroup whitelist. Docker-DCO-1.1-Signed-off-by: Kevin Wallace <kevin@pentabarf.net> (github: kevinwallace) |
||
|---|---|---|
| .. | ||
| cgroups | ||
| collections | ||
| graphdb | ||
| iptables | ||
| label | ||
| libcontainer | ||
| listenbuffer | ||
| mflag | ||
| mount | ||
| namesgenerator | ||
| netlink | ||
| proxy | ||
| selinux | ||
| signal | ||
| sysinfo | ||
| system | ||
| systemd | ||
| term | ||
| user | ||
| version | ||
| README.md | ||
README.md
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!