moby--moby/pkg
Brian Goff 2381c7f18d Merge pull request #26281 from LK4D4/fix_multireader_offset
pkg/ioutils: fix multireader SEEK_CUR branch
2016-09-06 20:47:03 -04:00
..
aaparser
archive
authorization Fix AuthZ plugins headers change issue 2016-08-23 21:08:23 -07:00
broadcaster
chrootarchive Use real chroot if daemon is running in a user namespace 2016-08-12 16:31:01 -04:00
devicemapper devmapper: prevent libdevmapper from deleting device symlinks in RemoveDeviceDeferred 2016-08-23 23:58:53 +08:00
directory
discovery
filenotify
fileutils
gitutils
graphdb
homedir
httputils
idtools Don't start daemon in userns mode if graphdir inaccessible 2016-08-24 11:25:30 -04:00
integration Change to use c.Assert() instead of result.Assert() 2016-08-23 15:12:36 -04:00
ioutils pkg/ioutils: fix multireader SEEK_CUR branch 2016-09-06 11:08:35 -07:00
jsonlog
jsonmessage
listeners
locker
longpath
loopback
mount
namesgenerator Add Joan Clarke to name collection 2016-08-24 01:58:48 -07:00
parsers
pidfile
platform
plugins Fix govet for go1.7 2016-09-02 19:07:54 -07:00
pools
progress
promise
pubsub
random
reexec
registrar
signal
stdcopy
streamformatter
stringid
stringutils
symlink
sysinfo
system Add system.Stat support for darwin/macOS 2016-08-24 11:25:26 -04:00
tailfile
tarsum
term
testutil Add testutil/tempfile 2016-08-25 13:09:03 -04:00
tlsconfig Fix govet for go1.7 2016-09-02 19:07:54 -07:00
truncindex
urlutil
useragent
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!