moby--moby/pkg
Victor Vieux d2327006d6 Merge pull request #4442 from ibuildthecloud/hairpin-nat
Support hairpin NAT without going through docker server
2014-03-27 18:09:42 -07:00
..
cgroups cgroups: Add systemd implementation of cgroups 2014-03-27 22:44:31 +01:00
collections
graphdb runtime: Fix unique constraint error checks 2014-03-03 15:10:52 +01:00
iptables Support hairpin NAT without going through docker server 2014-03-03 21:53:57 -07:00
label This patch adds SELinux labeling support. 2014-03-26 15:30:40 -04:00
libcontainer cgroups: Splity out Apply/Cleanup to separate file/interface 2014-03-27 21:47:47 +01:00
listenbuffer adding configuration for timeout and disable it by default 2014-03-17 15:12:02 -07:00
mflag update godoc and add MAINTAINERS for mflags 2014-03-14 17:35:41 +00:00
mount
namesgenerator
netlink Update email + add self to pkg/signal 2014-03-10 20:26:45 -07:00
proxy Remove verbose logging for non errors 2014-02-17 13:31:13 -08:00
selinux This patch adds SELinux labeling support. 2014-03-26 15:30:40 -04:00
signal Like signal_linux.go, we don't have import os and os/signal 2014-03-11 23:14:58 +09:00
sysinfo
system Send sigterm to child instead of sigkill 2014-03-14 15:42:05 -07:00
systemd Add systemd.SdBooted() 2014-03-27 22:44:31 +01:00
term Use BSD raw mode on darwin. Fixes nano, tmux and others 2014-03-13 11:11:02 -07:00
user
version add version pkg 2014-02-25 21:08:38 +00:00
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!