The toolkit to pack, ship, store, and deliver container content
Find a file
Milos Gajdos 08f5645587
Merge pull request #3893 from pluralsh/part-pagination
[release/2.8] Add code to handle pagination of parts. Fixes max layer size of 10GB bug
2023-05-09 20:58:24 +01:00
.github/workflows Merge pull request #3893 from pluralsh/part-pagination 2023-05-09 20:58:24 +01:00
cmd Fix gofmt warnings 2023-05-09 18:58:38 +01:00
configuration Fix gofmt warnings 2023-05-09 18:58:38 +01:00
context Fix gofmt warnings 2023-05-09 18:58:38 +01:00
contrib fix go check issues 2021-11-16 17:46:08 +08:00
digestset Enable static checks 2018-08-06 14:49:11 -07:00
docs Change should to must in v2 spec 2021-09-08 15:24:07 +02:00
health Fix gofmt warnings 2023-05-09 18:58:38 +01:00
manifest manifest: validate document type before unmarshal 2021-11-05 10:16:09 -07:00
metrics Add Prometheus Metrics 2018-02-09 14:27:51 -08:00
notifications Fix gometalint errors 2021-03-23 21:03:10 +08:00
project bump up golang version 2023-05-09 10:59:43 +02:00
reference Fix gofmt warnings 2023-05-09 18:58:38 +01:00
registry Merge pull request #3893 from pluralsh/part-pagination 2023-05-09 20:58:24 +01:00
releases FIx typo 2022-03-08 17:14:24 +00:00
script bump up golang version 2023-05-09 10:59:43 +02:00
testutil Enable static checks 2018-08-06 14:49:11 -07:00
uuid Only enable uuid generation warning when using registry handlers 2015-07-30 14:27:07 -07:00
vendor Merge pull request #3466 from thaJeztah/2.7_update_jwt 2021-11-23 09:10:53 +00:00
version Fix gofmt warnings 2023-05-09 18:58:38 +01:00
.dockerignore Dockerfile: switch to xx 2023-05-09 10:59:42 +02:00
.gitignore add s3 region filters for cloudfront 2017-12-01 15:58:58 -08:00
.golangci.yml [release/2.8] ignore deprecation of io/ioutil 2023-05-09 17:57:28 +02:00
.mailmap Prepare for v2.8.1 release 2022-02-24 13:44:40 +00:00
blobs.go Migrate to golangci-lint 2021-03-23 21:02:54 +08:00
BUILDING.md fix out of date cli arg for registry version 2018-02-28 06:46:06 +08:00
CONTRIBUTING.md Update CONTRIBUTING.md 2017-12-29 14:41:43 +02:00
doc.go fix some typos in source comments 2015-04-17 12:39:52 +00:00
docker-bake.hcl Dockerfile: switch to xx 2023-05-09 10:59:42 +02:00
Dockerfile update to go1.19.9 2023-05-09 17:57:57 +02:00
errors.go disable schema1 by default, add a config flag to enable it 2017-12-19 10:23:25 -08:00
LICENSE Initial commit 2014-12-22 15:49:26 -08:00
MAINTAINERS Add new reviewers 2018-08-20 12:24:15 -07:00
Makefile bump up golang version 2023-05-09 10:59:43 +02:00
manifests.go Fix gometalint errors 2021-03-23 21:03:10 +08:00
README.md Update README so the release pipeline works properly. 2022-02-07 15:40:21 +00:00
registry.go add support for repo deleted event also 2018-08-02 23:05:05 -07:00
ROADMAP.md fix typos 2016-06-02 23:03:27 +08:00
tags.go context: remove definition of Context 2017-08-11 15:53:31 -07:00
vendor.conf Merge pull request #3466 from thaJeztah/2.7_update_jwt 2021-11-23 09:10:53 +00:00

Distribution

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

This repository provides 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.