Files
docker-cli/components/engine/pkg
Drew Erny f9c823322f fix docker logs error handling
Previously, `docker logs` (and by extension, `docker service logs`) had
an error in the way they returned errors that occurred after a stream
had already been started. Specifically, the errors were added verbatim
to the HTTP response, which caused StdCopy to fail with an esoteric
error. This change updates StdCopy to accept errors from the source
stream and then return those errors when copying to the destination
stream.

Signed-off-by: Drew Erny <drew.erny@docker.com>
Upstream-commit: f19b0d72d1234c2bf4d85f7c1a4916b7b85b97b0
Component: engine
2017-02-14 14:38:42 -08:00
..
2017-01-19 15:52:28 +08:00
2016-12-27 17:32:15 +08:00
2016-12-02 03:58:54 -08:00
2017-01-18 00:13:09 +08:00
2017-01-24 11:16:19 +01:00
2017-02-07 21:58:56 +01:00
2016-12-28 09:43:27 +08:00
2016-06-11 13:16:55 -07:00
2015-12-13 18:04:12 +02:00
2016-04-09 21:18:15 +08:00
2016-11-16 12:55:18 -05:00
2017-02-14 14:38:42 -08:00
2017-02-07 21:58:56 +01:00
2016-11-30 10:11:42 -08:00
2016-11-13 20:08:51 -08:00
2017-01-19 15:52:28 +08:00
2016-04-28 11:04:50 +08: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!