The toolkit to pack, ship, store, and deliver container content
Find a file
davidli 79d4d7f546 driver/swift: treat empty object list as a PathNotFoundError
Swift returns an empty object list when trying to read a non-existing object path, treat it as a
PathNotFoundError when trying to list a non existing virtual directory.

Signed-off-by: David li <wenquan.li@hpe.com>
2015-12-08 12:04:04 -08:00
cmd Storage driver for: Google Cloud Storage (gcs) 2015-10-28 20:21:56 +00:00
configuration Add http.host parameter 2015-09-30 15:12:01 -07:00
context Add go version to logger output 2015-10-22 10:11:25 -07:00
contrib Download dind from v1.8.1 tag of docker/docker repo 2015-09-08 17:48:13 -07:00
digest Validate digest length on parsing 2015-12-02 16:04:06 -08:00
docs Merge pull request #1234 from SvenDowideit/linkchecker-fixes 2015-12-05 09:30:58 +10:00
Godeps Update Swift bindings 2015-11-03 09:57:39 +01:00
health Add headers parameter for HTTP checker 2015-08-20 15:11:16 -07:00
manifest Before allowing a schema1 manifest to be stored in the registry, ensure that it 2015-11-03 15:19:46 -08:00
notifications Before allowing a schema1 manifest to be stored in the registry, ensure that it 2015-11-03 15:19:46 -08:00
project Adds pre-commit hook, hook config script, and a README 2014-12-15 18:09:11 -08:00
reference reference: refactor grammar and regular expressions 2015-12-04 17:54:23 -08:00
registry driver/swift: treat empty object list as a PathNotFoundError 2015-12-08 12:04:04 -08:00
testutil Add pull through cache functionality to the Registry which can be configured 2015-08-04 16:09:55 -07:00
uuid Only enable uuid generation warning when using registry handlers 2015-07-30 14:27:07 -07:00
version Rev base version to 2.1.0 2015-08-06 17:21: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 Fix double entry in AUTHORS file 2015-08-07 14:00:07 -07:00
AUTHORS Update authors 2015-11-02 16:05:34 -08:00
blobs.go Change some incorrect error types in proxy stores from API errors to 2015-08-11 14:16:24 -07:00
circle.yml Use go 1.5 on the build machine 2015-11-11 09:50:59 -08:00
CONTRIBUTING.md Forbid commenting on closed issues 2015-08-12 10:45:42 -07:00
doc.go fix some typos in source comments 2015-04-17 12:39:52 +00:00
Dockerfile Storage driver for: Google Cloud Storage (gcs) 2015-10-28 20:21:56 +00:00
errors.go Define error type 2015-12-01 22:23:38 +01:00
LICENSE Initial commit 2014-12-22 15:49:26 -08:00
MAINTAINERS Update authors 2015-11-02 16:41:36 -08:00
Makefile Use go 1.5 on the build machine 2015-11-11 09:50:59 -08:00
README.md README: fix formatting of docker-registry link 2015-11-20 17:18:25 -08:00
registry.go Move manifest package to schema1 2015-08-21 16:29:47 -07:00
ROADMAP.md Update distribution roadmap. 2015-10-27 17:20:49 -07: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.