Skip to content
The Docker toolset to pack, ship, store, and deliver content
Branch: master
Clone or download
caervs Merge pull request #2849 from Shawnpku/master
support Alibaba Cloud CDN storage middleware
Latest commit 3226863 Apr 16, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
cmd import alicdn package Mar 19, 2019
configuration Fix gometalint errors Feb 5, 2019
context remove closenotifier Sep 11, 2018
contrib
digestset
docs
health
manifest Fix gometalint errors Feb 5, 2019
metrics Add Prometheus Metrics Feb 9, 2018
notifications
project Adds pre-commit hook, hook config script, and a README Dec 16, 2014
reference Merge pull request #2840 from manishtomar/fix-lint Feb 5, 2019
registry Merge pull request #2849 from Shawnpku/master Apr 17, 2019
releases Release notes for 2.7 Nov 30, 2018
script Update build to use travis Aug 1, 2018
testutil Enable static checks Aug 6, 2018
uuid Only enable uuid generation warning when using registry handlers Jul 30, 2015
vendor fix Context issue Mar 4, 2019
version Release notes for 2.7 Nov 30, 2018
.gitignore add s3 region filters for cloudfront Dec 1, 2017
.gometalinter.json Merge pull request #2662 from dmcgowan/enable-structcheck Aug 8, 2018
.mailmap Update mailmap file Sep 26, 2018
.travis.yml remove go 1.9 and 1.10 checks from travis Sep 11, 2018
BUILDING.md fix out of date cli arg for registry version Feb 27, 2018
CONTRIBUTING.md Update CONTRIBUTING.md Dec 29, 2017
Dockerfile Add GOARM flag to dockerfile Nov 28, 2018
LICENSE Initial commit Dec 22, 2014
MAINTAINERS
Makefile
README.md DOC: README: Fix broken link in migrator Apr 5, 2017
ROADMAP.md fix typos Jun 2, 2016
blobs.go Merge pull request #2328 from stepyu/patch-1 Aug 23, 2018
doc.go
errors.go disable schema1 by default, add a config flag to enable it Dec 19, 2017
manifests.go
registry.go add support for repo deleted event also Aug 3, 2018
tags.go context: remove definition of Context Aug 11, 2017
vendor.conf fix ci issue Mar 4, 2019

README.md

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.

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.

You can’t perform that action at this time.