Files
docker-cli/components/engine/pkg
Josh Hawn c13d2851b8 Add Tarsum Calculation during v2 Pull operation
While the v2 pull operation is writing the body of the layer blob to disk
it now computes the tarsum checksum of the archive before extracting it to
the backend storage driver. If the checksum does not match that from the
image manifest an error is raised.

Also adds more debug logging to the pull operation and fixes existing test
cases which were failing. Adds a reverse lookup constructor to the tarsum
package so that you can get a tarsum object using a checksum label.

Docker-DCO-1.1-Signed-off-by: Josh Hawn <josh.hawn@docker.com> (github: jlhawn)
Upstream-commit: 213e3d116642431adbe634d39740eddc5a81e063
Component: engine
2015-01-15 14:05:05 -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
2015-01-13 15:40:24 +08:00
2014-12-06 22:52:19 +08:00
2014-10-24 15:03:06 -07:00
2015-01-12 22:47:36 +00: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!