docs/pkg
Brian Goff a07e963526 Merge pull request #11882 from hqhq/hq_warn_device_cg
add devices cgroup check as hard requirement
2015-04-27 18:42:57 -04:00
..
archive trivial: typo cleanup 2015-04-27 13:35:08 -07:00
broadcastwriter
chrootarchive
devicemapper
directory
etchosts
fileutils
graphdb trivial: typo cleanup 2015-04-27 13:35:08 -07:00
homedir
httputils
ioutils
iptables Merge pull request #9397 from jpopelka/9395-firewalld 2015-04-23 16:58:08 -04:00
jsonlog Small if err cleaning 2015-04-27 21:50:33 +02:00
jsonmessage
listenbuffer
mflag Small if err cleaning 2015-04-27 21:50:33 +02:00
mount
namesgenerator
parsers Replace json.Unmarshal with json.Decoder().Decode() 2015-04-26 15:02:01 +02:00
pidfile
pools
progressreader
promise
proxy
pubsub
reexec
requestdecorator
resolvconf
signal
stdcopy
streamformatter
stringid
stringutils
symlink
sysinfo simplify memory limit check 2015-04-24 08:43:44 +08:00
system Small if err cleaning 2015-04-27 21:50:33 +02:00
systemd
tailfile
tarsum
term trivial: typo cleanup 2015-04-27 13:35:08 -07:00
timeoutconn Small if err cleaning 2015-04-27 21:50:33 +02:00
timeutils
truncindex
ulimit
units
urlutil
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!