moby--moby/pkg
Tianon Gravi 8e967fe802 Revert "Always mount a /run tmpfs in the container"
This reverts commit 905795ece6.

Docker-DCO-1.1-Signed-off-by: Andrew Page <admwiggin@gmail.com> (github: tianon)
2014-05-21 14:28:19 -06:00
..
apparmor Apply apparmor before restrictions 2014-05-01 19:09:12 -07:00
beam Use int64 instead of int 2014-05-11 06:23:53 -07:00
collections Refactoring collections/orderedintset and benchmarks for it 2014-05-14 06:04:12 +04:00
dockerscript Fix various MAINTAINERS format inconsistencies 2014-04-30 11:22:11 -06:00
graphdb FIXES #5398: pkg/graphdb build only dependent on cgo tag 2014-04-30 11:57:10 -06:00
iptables
label
libcontainer Revert "Always mount a /run tmpfs in the container" 2014-05-21 14:28:19 -06:00
listenbuffer
mflag use tabwriter to display usage in mflag 2014-05-06 21:31:21 +00:00
mount
namesgenerator
netlink
networkfs pkg: networkfs: etchosts: fixed tests 2014-05-07 00:42:22 +10:00
proxy
selinux
signal Fix various MAINTAINERS format inconsistencies 2014-04-30 11:22:11 -06:00
symlink Fixes 5370 infinite/maxLoopCount loop for relative symlinks 2014-05-16 01:03:11 +02:00
sysinfo Move cgroups package into libcontainer 2014-05-14 15:21:44 -07:00
system Add GetParentDeathSignal() to pkg/system 2014-05-15 10:17:44 +02:00
systemd
term
units Move duration and size to units pkg 2014-05-12 17:05:07 -07:00
user Check uid ranges 2014-05-18 20:49:08 +04:00
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!