The toolkit to pack, ship, store, and deliver container content
Find a file
Noah Treuhaft ad6bb66faf Add notification filtering by target media type
The Hub registry generates a large volume of notifications, many of
which are uninteresting based on target media type.  Discarding them
within the notification endpoint consumes considerable resources that
could be saved by discarding them within the registry.  To that end,
this change adds registry configuration options to restrict the
notifications sent to an endpoint based on target media type.

Signed-off-by: Noah Treuhaft <noah.treuhaft@docker.com>
2016-09-16 12:01:03 -07:00
cmd Load the middleware/redirect driver 2016-07-19 15:37:10 +01:00
configuration Add notification filtering by target media type 2016-09-16 12:01:03 -07:00
context Fix vet errors with go 1.7 2016-07-18 13:41:19 -07:00
contrib Add v1 search with v2 token auth test 2016-07-13 17:03:14 -07:00
digest Typo fixes in comments 2016-02-10 16:26:29 -08:00
docs Add notification filtering by target media type 2016-09-16 12:01:03 -07:00
Godeps Vendor update for aws sdk 2016-07-12 12:47:37 -07:00
health fix typos 2016-06-02 23:03:27 +08:00
manifest upate plugin MediaType 2016-09-06 03:34:24 -07:00
notifications Add notification filtering by target media type 2016-09-16 12:01:03 -07:00
project Adds pre-commit hook, hook config script, and a README 2014-12-15 18:09:11 -08:00
reference Improve "invalid reference" error message 2016-09-12 15:13:14 +02:00
registry Add notification filtering by target media type 2016-09-16 12:01:03 -07:00
testutil testutil, storage: use math/rand.Read where possible 2016-08-10 14:26:12 -07:00
uuid Only enable uuid generation warning when using registry handlers 2015-07-30 14:27:07 -07:00
vendor Vendor update for aws sdk 2016-07-12 12:47:37 -07:00
version Update AUTHORS and version file 2016-05-04 10:22:07 -07: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 Prepare for the release. 2016-06-13 16:03:16 -07:00
blobs.go Provide stat descriptor for Create method during cross-repo mount (#1857) 2016-08-01 19:07:11 -07:00
BUILDING.md Move the building.md doc to the top of the git repo 2016-06-15 20:26:16 +10:00
CHANGELOG.md Changelog for 2.5 2016-06-13 15:37:26 -07:00
circle.yml Disable registry handlers race tests 2016-08-29 13:41:53 -07: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 reorder Dockerfile steps for better layer caching 2016-07-22 13:51:31 -04:00
errors.go Defined ErrAccessDenied error 2016-02-22 21:12:59 +01:00
Jenkinsfile Add docs checking Jenkinsfile 2016-08-22 12:19:30 +10: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 Makefile: don't look for golint and godep in specific places 2016-03-31 11:00:28 -07:00
manifests.go Remove signature store from registry. Return a generated signature for manifest 2016-05-27 13:19:26 -07:00
README.md fixes link to building.md 2016-09-06 11:16:03 -05:00
registry.go Update documentation and examples in notifications.md 2016-03-23 15:51:32 -07: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

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.