8ae8751b21
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) |
||
---|---|---|
archive | ||
broadcastwriter | ||
chrootarchive | ||
devicemapper | ||
fileutils | ||
graphdb | ||
httputils | ||
ioutils | ||
iptables | ||
jsonlog | ||
listenbuffer | ||
mflag | ||
mount | ||
namesgenerator | ||
networkfs | ||
parsers | ||
pools | ||
promise | ||
proxy | ||
reexec | ||
signal | ||
stdcopy | ||
symlink | ||
sysinfo | ||
system | ||
systemd | ||
tailfile | ||
tarsum | ||
term | ||
testutils | ||
timeutils | ||
truncindex | ||
units | ||
urlutil | ||
version | ||
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!