moby--moby/pkg
Tibor Vass 7410f1a859 pkg/archive: keep walkRoot clean if source is /
Previously, getWalkRoot("/", "foo") would return "//foo"
Now it returns "/foo"

Signed-off-by: Tibor Vass <tibor@docker.com>
2019-06-14 03:57:58 +00:00
..
aaparser
archive pkg/archive: keep walkRoot clean if source is / 2019-06-14 03:57:58 +00:00
authorization
broadcaster
capabilities Add more import comments 2019-04-10 16:59:33 +02:00
chrootarchive Add chroot for tar packing operations 2019-06-03 09:45:29 -07:00
containerfs
devicemapper
directory
discovery
dmesg
filenotify
fileutils
fsutils
homedir
idtools Stop sorting uid and gid ranges in id maps 2019-06-03 15:50:26 +02:00
ioutils
jsonmessage
locker
longpath
loopback
mount Fix to gofmt/goimports errors 2019-05-28 20:32:27 +03:00
namesgenerator Add Satoshi Nakamoto to names generator 2019-04-23 10:32:53 +02:00
parsers Adding OS version info to the nodes' `Info` struct 2019-06-06 22:40:10 +00:00
pidfile
platform
plugingetter
plugins
pools
progress
pubsub
reexec
signal
stdcopy
streamformatter
stringid Entropy cannot be saved 2019-06-07 11:54:45 +01:00
symlink
sysinfo Start containers in their own cgroup namespaces 2019-05-07 10:22:16 -07:00
system LCOW: (Experimental) Require RS5+ builds 2019-04-18 09:43:37 -07:00
tailfile
tarsum
term
truncindex Entropy cannot be saved 2019-06-07 11:54:45 +01:00
urlutil
useragent
README.md

README.md

pkg/ is a collection of utility packages used by the Moby project without being specific to its internals.

Utility packages are kept separate from the moby 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 Moby 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!