an [abandoned] attempt to slice out the docker/docker/pkg package
Find a file
Phil Estes 8ae8751b21 Update container resolv.conf when host network changes /etc/resolv.conf
Only modifies non-running containers resolv.conf bind mount, and only if
the container has an unmodified resolv.conf compared to its contents at
container start time (so we don't overwrite manual/automated changes
within the container runtime). For containers which are running when
the host resolv.conf changes, the update will only be applied to the
container version of resolv.conf when the container is "bounced" down
and back up (e.g. stop/start or restart)

Docker-DCO-1.1-Signed-off-by: Phil Estes <estesp@linux.vnet.ibm.com> (github: estesp)
2015-01-08 14:15:13 -05:00
archive Refactor to optimize storage driver ApplyDiff() 2014-12-17 21:54:23 -08:00
broadcastwriter Mass gofmt 2014-10-24 15:11:48 -07:00
chrootarchive Refactor to optimize storage driver ApplyDiff() 2014-12-17 21:54:23 -08:00
devicemapper devmapper: Use device id as specified by caller 2014-12-03 13:06:43 -05:00
fileutils Use logrus everywhere for logging 2014-10-24 15:03:06 -07:00
graphdb pkg/graphdb: use transactions for transactions 2014-12-19 13:57:21 +02:00
httputils Use logrus everywhere for logging 2014-10-24 15:03:06 -07:00
ioutils pkg/ioutils: add ReaderErrWrapper to readers 2014-09-03 11:36:21 +03:00
iptables Create tests for pkg/iptables 2014-12-21 12:57:32 +10:00
jsonlog update sysinfo to logrus 2014-10-27 18:59:02 +00:00
listenbuffer adding configuration for timeout and disable it by default 2014-03-17 15:12:02 -07:00
mflag flag: fix the comments 2014-11-30 01:58:16 +08:00
mount Fix output format where no variable specified in mount pkg 2014-12-03 19:02:51 -08:00
namesgenerator pkg/namesgenerator: add Yeong-Sil Jang 2014-11-08 16:36:41 +02:00
networkfs Update container resolv.conf when host network changes /etc/resolv.conf 2015-01-08 14:15:13 -05:00
parsers Cleanup ParseHost 2014-11-25 18:55:40 -05:00
pools pkg/pool: add pools for bufio readers & writers 2014-09-03 11:36:39 +03:00
promise Move Go() promise-like func from utils to pkg/promise 2014-09-29 23:16:27 -07:00
proxy pkg/proxy: Bump the maximum size of a UDP packet. 2014-10-31 18:56:07 +00:00
reexec add pkg/chrootarchive and use it on the daemon 2014-11-25 01:03:40 +02:00
signal Removed race condition 2014-12-06 22:52:19 +08:00
stdcopy Use logrus everywhere for logging 2014-10-24 15:03:06 -07:00
symlink Fix vet errors about formatting directives 2014-12-12 10:58:56 -08:00
sysinfo update sysinfo to logrus 2014-10-27 18:59:02 +00:00
system pkg/system: fix cleanup in tests 2014-11-20 19:33:15 +02:00
systemd Add systemd.SdBooted() 2014-03-27 22:44:31 +01:00
tailfile Implement tail for docker logs 2014-07-01 23:44:12 +04:00
tarsum pkg/tarsum: delete the logging code 2014-12-18 23:38:26 +02:00
term Use termios via CGO only on Linux 2014-11-25 20:49:01 +09:00
testutils Graphtest is ok to compile normally 2014-08-07 14:33:09 -07:00
timeutils pkg/timeutils: lint and add comments 2014-10-06 22:27:56 +03:00
truncindex pkg/truncindex: lint and add comments 2014-10-06 22:00:58 +03:00
units pkg/units: fix size_test.go compilation 2014-12-19 18:38:12 +02:00
urlutil Move git and url checks into pkg 2014-11-24 18:10:37 -05:00
version pkg/version: lint and add comments 2014-10-06 18:41:53 +03:00
README.md Add README to pkg 2013-12-23 23:12:19 +00:00

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!