The toolkit to pack, ship, store, and deliver container content
Find a file
Richard e0b3f40994 Ensure the instrumentedResponseWriter correctly sets the http
status in the context.

Signed-off-by: Richard Scothern <richard.scothern@gmail.com>
2015-05-06 11:04:51 -07:00
cmd Add configuration for upload purging 2015-05-06 11:04:51 -07:00
configuration Add configuration for upload purging 2015-05-06 11:04:51 -07:00
context Ensure the instrumentedResponseWriter correctly sets the http 2015-05-06 11:04:51 -07:00
contrib/compose Updating with new RC work 2015-04-16 10:44:30 -07:00
digest fix some typos in source comments 2015-05-06 11:04:49 -07:00
docs Update API spec to reference digest instead of tarsum 2015-05-06 11:04:51 -07:00
Godeps Update goamz package dependency 2015-05-06 11:04:50 -07:00
health Adding first version of HealthCheck 2015-03-20 14:38:40 -07:00
manifest Specify manifest schema version 1 media type 2015-02-19 16:47:13 -08:00
notifications Address possible goroutine leak in notification library 2015-05-06 11:04:51 -07:00
project Adds pre-commit hook, hook config script, and a README 2014-12-15 18:09:11 -08:00
registry Ensure the instrumentedResponseWriter correctly sets the http 2015-05-06 11:04:51 -07:00
testutil Move testutil package to top-level 2015-01-05 16:53:13 -08:00
version Update rough version for release 2015-04-16 11:25:03 -07:00
.drone.yml Fix goverall 2014-11-22 10:17:14 -08:00
.gitignore Improve context package 2015-04-01 15:40:21 -07:00
.mailmap Update AUTHORS file for releease. 2015-04-16 11:23:56 -07:00
AUTHORS Update AUTHORS file for releease. 2015-04-16 11:23:56 -07:00
circle.yml Move to godep 2015-01-22 15:52:46 -08:00
CONTRIBUTING.md Update Sprint label link from Ready 2015-03-17 18:56:56 -07:00
doc.go fix some typos in source comments 2015-05-06 11:04:49 -07:00
Dockerfile Use entrypoint in Dockerfile 2015-04-06 23:06:18 +01:00
errors.go Add error return to Repository method on Registry 2015-02-13 16:27:33 -08:00
LICENSE Initial commit 2014-12-22 15:49:26 -08:00
MAINTAINERS Add Stephen Day to maintainers file 2015-01-28 10:31:54 -08:00
Makefile Update final upload chunk api doc 2015-04-15 17:55:15 -07:00
README.md Updating with new RC work 2015-04-16 10:44:30 -07:00
registry.go Rename top level registry interface to namespace 2015-04-09 19:21:33 -07:00
ROADMAP.md more formatting... 2015-03-18 19:02:37 -07:00

Distribution

The Docker toolset to pack, ship, store, and deliver content.

This repository's main product is the Docker Registry Service 2.0 implementation for storing and distributing Docker images. It supersedes the docker/docker- registry project with a new API design, focused around security and performance.

This repository contains the following components:

Component Description
registry An implementation of the Docker Registry HTTP API V2 for use with docker 1.6+.
libraries A rich set of libraries for interacting with,distribution components. Please see godoc for details. Note: These libraries are unstable.
dist An experimental tool to provide distribution, oriented functionality without the docker daemon.
specifications Distribution related specifications are available in docs/spec
documentation Docker's full documentation set is available at docs.docker.com. This repository contains the subset related just to the registry.

How does this integrate with Docker engine?

This project should provide an implementation to a V2 API for use in the Docker core project. The API should be embeddable and simplify the process of securely pulling and pushing content from docker daemons.

What are the long term goals of the Distribution project?

The Distribution project has the further long term goal of providing a secure tool chain for distributing content. The specifications, APIs and tools should be as useful with Docker as they are without.

Our goal is to design a professional grade and extensible content distribution system that allow users to:

  • Enjoy an efficient, secured and reliable way to store, manage, package and exchange content
  • Hack/roll their own on top of healthy open-source components
  • Implement their own home made solution through good specs, and solid extensions mechanism.

More about Registry 2.0

The new registry implementation provides the following benefits:

  • faster push and pull
  • new, more efficient implementation
  • simplified deployment
  • pluggable storage backend
  • webhook notifications

For information on upcoming functionality, please see ROADMAP.md.

Who needs to deploy a registry?

By default, Docker users pull images from Docker's public registry instance. Installing Docker gives users this ability. Users can also push images to a repository on Docker's public registry, if they have a Docker Hub account.

For some users and even companies, this default behavior is sufficient. For others, it is not.

For example, users with their own software products and may want to maintain an registry for private, company images. Also, you may wish to deploy your own image repository for images used to test or in continuous integration. For these use cases and others, deploying your own registry instance may be the better choice.

Contribute

Please see CONTRIBUTING.md.

Support

If any issues are encountered while using the Distribution project, several avenues are available for support:

IRC #docker-distribution on FreeNode
Issue Tracker github.com/docker/distribution/issues
Google Groups https://groups.google.com/a/dockerproject.org/forum/#!forum/distribution
Mailing List docker@dockerproject.org

License

This project is distributed under Apache License, Version 2.0.