The toolkit to pack, ship, store, and deliver container content
Find a file
Aaron Lehmann 245ca4659e reference: Replace EnsureTagged with TagNameOnly
The common use case for this function is to add a default tag if the
reference only has a name. The current behavior only adds the default
tag if there is no *tag*, which requires most callers to check for a
digest. Change the behavior to only add default tags to name-only
references, and change the name to reflect this. The documentation
already described the new behavior, so it does not need to be changed.

Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>
2017-01-26 11:46:00 -08:00
cmd digest: migrate to opencontainers/go-digest 2017-01-06 15:42:03 -08:00
configuration registry/handles/app: always append default urls regexps 2016-12-05 20:28:51 +01:00
context Fix vet errors with go 1.7 2016-07-18 13:41:19 -07:00
contrib Remove container after export 2017-01-09 16:44:37 -08:00
digestset digest: migrate to opencontainers/go-digest 2017-01-06 15:42:03 -08:00
docs Improve formatting of configuration.md 2016-12-29 11:32:31 -08:00
health Documentation fix for package 'health'. Use proper import path for 'health/api' 2017-01-16 18:38:22 +01:00
manifest Update registry to use WithName for creating Named values 2017-01-18 13:56:56 -08:00
notifications Update registry to use WithName for creating Named values 2017-01-18 13:56:56 -08:00
project Adds pre-commit hook, hook config script, and a README 2014-12-15 18:09:11 -08:00
reference reference: Replace EnsureTagged with TagNameOnly 2017-01-26 11:46:00 -08:00
registry Update handler test to use WithName 2017-01-19 15:21:40 -08:00
testutil digest: migrate to opencontainers/go-digest 2017-01-06 15:42:03 -08:00
uuid Only enable uuid generation warning when using registry handlers 2015-07-30 14:27:07 -07:00
vendor Update aws-sdk-go dependency to 1.6.12 2017-01-18 14:49:28 -05:00
version Release preperation: update AUTHORS and version file 2016-11-11 09:23:05 -08:00
.gitignore Improve context package 2015-04-01 15:40:21 -07:00
.mailmap Prepare for the release. 2016-06-13 16:03:16 -07:00
AUTHORS Release preperation: update AUTHORS and version file 2016-11-11 09:23:05 -08:00
blobs.go digest: migrate to opencontainers/go-digest 2017-01-06 15:42:03 -08:00
BUILDING.md Enable dependency validation 2016-11-23 15:45:04 -08:00
CHANGELOG.md Update release notes for 2.6 2017-01-17 16:16:05 -08:00
circle.yml Enable dependency validation 2016-11-23 15:45:04 -08:00
CONTRIBUTING.md Removes ceph rados driver in favor of Swift API gateway support 2016-03-10 16:49:08 -08:00
coverpkg.sh Fix codecov following vendor 2016-03-24 10:30:14 -07:00
doc.go fix some typos in source comments 2015-04-17 12:39:52 +00:00
Dockerfile Bump to go1.7 2016-10-31 13:05:03 -07:00
errors.go digest: migrate to opencontainers/go-digest 2017-01-06 15:42:03 -08:00
LICENSE Initial commit 2014-12-22 15:49:26 -08:00
MAINTAINERS Prepare for the release. 2016-06-13 16:03:16 -07:00
Makefile Enable dependency validation 2016-11-23 15:45:04 -08:00
manifests.go Correct the variable name. 2017-01-18 11:55:20 -08:00
README.md Fix broken doc links 2016-10-18 21:31:08 +09:00
registry.go fix misspell "lexicographically" in registry.go 2017-01-19 10:42:04 +08:00
RELEASE-CHECKLIST.md Document registry release process 2016-11-07 12:48:55 -08:00
ROADMAP.md fix typos 2016-06-02 23:03:27 +08:00
tags.go Implementation of the Manifest Service API refactor. 2015-12-17 17:09:14 -08:00
vendor.conf Update aws-sdk-go dependency to 1.6.12 2017-01-18 14:49:28 -05:00

Distribution

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

This repository's main product is the Docker Registry 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.

Circle CI GoDoc

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.
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 may want to maintain a 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.

Migration to Registry 2.0

For those who have previously deployed their own registry based on the Registry 1.0 implementation and wish to deploy a Registry 2.0 while retaining images, data migration is required. A tool to assist with migration efforts has been created. For more information see [docker/migrator] (https://github.com/docker/migrator).

Contribute

Please see CONTRIBUTING.md for details on how to contribute issues, fixes, and patches to this project. If you are contributing code, see the instructions for building a development environment.

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.