kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity
moby--moby/pkg
History
Anusha Ragunathan 0ef21eb0e3 Fix pluginv1 Windows volumes 
c54b717 caused a regression for pluginv1 on Windows, where extraneous
backslashes were added to BasePath of the plugin. For pluginv1 on windows,
BasePath() should return an empty string, since the plugin is fully aware
of the mount path. Also, unlike Linux where all paths are relative to "/",
Windows paths are dependent on system drives and mapped drives.

Fixes #30148

Signed-off-by: Anusha Ragunathan <anusha.ragunathan@docker.com>
2017-01-13 17:01:48 -08:00
..
aaparser pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
archive rectify function and variable referred in pkg/archive/changes_linux.go 2016-12-16 14:58:47 +08:00
authorization plugingetter: Avoid all caps for constant declarations 2017-01-04 10:19:04 -08:00
broadcaster
chrootarchive Use wrong ApplyLayer in diff_windows.go 2016-12-19 17:21:18 +08:00
devicemapper several function names fixed in devmapper.go 2016-12-21 10:45:28 +08:00
directory
discovery Update docker daemon to dockerd 2016-12-27 17:32:15 +08:00
filenotify It is errNoSuchWatch not errNoSuchPoller in filenotify/poller.go 2016-12-26 16:19:50 +08:00
fileutils Fix use of **/ in .dockerignore 2016-12-02 03:58:54 -08:00
fsutils pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
gitutils
graphdb Windows: Factor out sqlite 2016-12-01 09:38:08 -08:00
homedir gcplogs: forcibly set HOME on static UNIX binary 2016-12-29 03:17:26 +00:00
httputils Update docs and code to use application/x-tar in the build API 2017-01-10 06:40:06 +02:00
idtools pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
ioutils s/bCap/bLen/ 2016-11-17 21:05:09 +00:00
jsonlog
jsonmessage
listeners
locker fix some typos 2016-12-28 09:43:27 +08:00
longpath
loopback
mount
namesgenerator Add some adjectives to the namesgenerator 2016-11-24 18:38:04 +01:00
parsers
pidfile pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
platform Swap usage of LazyDLL and LoadDLL to LazySystemDLL. 2016-11-22 14:57:11 -08:00
plugingetter plugingetter: Avoid all caps for constant declarations 2017-01-04 10:19:04 -08:00
plugins Fix pluginv1 Windows volumes 2017-01-13 17:01:48 -08:00
pools
progress Implement content addressability for plugins 2016-12-23 13:29:58 -08:00
promise
pubsub
random
reexec First header should be a top level header 2016-11-22 09:33:21 +08:00
registrar
signal Move stack dump dir to exec root 2016-11-16 12:55:18 -05:00
stdcopy
streamformatter
stringid Move imageID validation to stringid pkg 2016-12-26 18:53:22 -08:00
stringutils change minor mistake of spelling 2016-12-20 21:05:19 +08:00
symlink
sysinfo Only show global warnings once 2016-11-30 10:11:42 -08:00
system make more package in system support darwin 2016-12-26 21:30:06 +08:00
tailfile
tarsum fix t.Errorf to t.Error in serveral _test.go 2016-11-14 17:54:43 +08:00
templates Move templates to pkg/templates 2016-12-12 09:34:03 +01:00
term Windows: Fix crash in docker system prune 2016-12-09 14:23:25 -08:00
testutil Merge pull request #29947 from vdemeester/integration-some-runCommandWithOutput-clean 2017-01-10 15:56:42 +01:00
tlsconfig
truncindex Fix non thread-safe Iteration around go-patricia 2017-01-09 17:06:50 +00:00
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!