Files
docker/pkg
Doug Davis 6d801a3caa Have .dockerignore support Dockerfile/.dockerignore
If .dockerignore mentions either then the client will send them to the
daemon but the daemon will erase them after the Dockerfile has been parsed
to simulate them never being sent in the first place.

an events test kept failing for me so I tried to fix that too

Closes #8330

Signed-off-by: Doug Davis <dug@us.ibm.com>
2015-01-06 10:57:48 -08:00
..
2014-10-24 15:11:48 -07:00
2014-12-21 12:57:32 +10:00
2014-10-27 18:59:02 +00:00
2014-11-30 01:58:16 +08:00
2014-11-06 11:36:09 -08:00
2014-12-06 22:52:19 +08:00
2014-10-24 15:03:06 -07:00
2014-10-27 18:59:02 +00:00
2014-11-20 19:33:15 +02:00
2014-03-27 22:44:31 +01:00
2014-07-01 23:44:12 +04:00
2014-11-25 20:49:01 +09:00
2014-11-24 18:10:37 -05:00
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!