Tags

Bug fixes:

Allow uppercase characters in hostnames … 34c3acf
Fix schema1 manifest etag and docker content digest header … d7eb5d1
Add option to disable signatures … d1c1730
To avoid any network use unless necessary, delay establishing authori… … 740ed69
Extend authChallenger interface to remove type cast. … 16445b6
Enable proxying registries to downgrade fetched manifests to Schema 1. … 3693621

Docker Registry v2.3.0

What’s new?

This Docker Registry release is the first to support the Image Manifest Version 2, Schema 2
manifest format.

This new schema version has two primary goals. The first is to move the Docker
engine towards content-addressable images, by supporting an image model where
the image's configuration can be hashed to generate an ID for the image. The
second is to allow multi-architecture images, through a "fat manifest" which
references image manifests for platform-specific versions of an image.

For details, see https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md

Cross Repository Blob Mount

Previously the registry required all blob data to be uploaded to a repository,
even if it existed in the Registry’s blob store.  This was a security measure to
ensure the clients owned the data they intended to upload.

Cross Repository Mount now enables an existing blob to be mounted into the target
repository if it already exists in a repository which the user has pull access
to.  This can reduce the amount of data transferred when pushing images.

For details, see: https://github.com/docker/distribution/issues/634

Additionally there are a number of performance improvements, bug fixes and
documentation updates.

Gotchas

In certain cases, pull by digest will not work.  For details, see
https://github.com/docker/distribution/blob/master/docs/compatibility.md

Fixes a bug where the incorrect digest and size were sent in manifest push
events for schema 1 manifests.

A bug is fixed where the incorrect content type for Schema 1 manifests was
returned.

Docker Registry v2.3 alpha release with support for multiple architectures
and cross repository blob mounting.

Docker Registry v2.2.1

Patch release of Docker Registry 2.2 incorporating bug fixes, documentation and
performance improvements.  Official distributions of this release will be built
with go 1.5.2.

Docker Registry v2.2

This Docker Registry release brings a new storage driver implementation to the
Docker Registry along with bug fixes, documentation enhancements and logging
improvements.

What’s new?

Google Cloud Storage Driver
The Registry now supports Google's reliable and fast network and storage
infrastructure for layer and manifest storage.

Read-only mode
Enables a Registry to serve only read requests, useful to maintain read
availability during unsafe administrative tasks.

Configurable hostname support
Allows the specification of an externally-reachable URL for the Registry.

Improved handling of environmental variables
Enables environment variables to be specified which are not part of the
configuration file.

Configurable file-existence and HTTP health checks
Allows administrators to easily disable a registry temporarily by placing a file
on the filesystem.  Additionally a registry can be configured to check the
health of other services, such as notification endpoints.

Enable configurable HTTP headers to be set in responses
This feature is usable for Registry administrators to set response headers for
various uses cases including increased security.

Redirect Support in the Swift Driver
The Swift storage driver now supports generating download URLs in line with
other cloud storage drivers.

Gotchas

In order to support valid hostnames as name components, supporting repeated dash
was added.  Additionally double underscore is now allowed as a separator to
loosen the restriction for previously supported names.

v2.1.1: Patch release of Docker Registry 2.1

This release provides a bug fix where the filesystem layout of manifests was
not backwards compatible with v2.0.x registries.

Docker Registry v2.1

The Docker Registry release brings some major new features to the Docker
Registry along with numerous bug fixes, documentation enhancements and logging
improvements.  More than 150 pull requests were completed by more than 50
contributors.

What’s new?

Support for listing Registry repositories
A specification and implementation of the catalog API allows users to list the
contents of a Registry

Manifest and Layer soft deletion
Manifests and layers can now be deleted by reference.

Pull through caching (experimental)
The Registry can now act as a pull through cache, proxying content from the
Docker Hub.

Storage Drivers
The following storage drivers were contributed to the distribution project by
members of the open source community.

Aliyun OSS.   Open Storage Service (OSS) is a massive, secure and highly
reliable cloud storage service provided by Aliyun.

Ceph.  Ceph is a free software storage platform designed to present object,
block, and file storage from a single distributed computer cluster.

Openstack Swift.  Swift is a highly available, distributed, eventually
consistent object/blob store from Openstack.

And many more...
- API specification clarifications
- Etag support for layers and manifests
- htpasswd support with bcrypt
- Unix socket support
- Client disconnection detection
- A slimmer official image
- Faster push for multi-tagged images

Things to pay close attention to if you are upgrading

If you are running multiple registries behind a load balancer, you need to make
sure that you explicitly specified the same secret for all nodes as per the
configuration documentation (commit).

The Length field in the Notification JSON is being deprecated in favor of Size.
Both are supported in this release (commit).

The location of the config file inside the official image has changed. If you
previously mounted an external configuration file with a volume, you need to
update the location to /etc/docker/registry/config.yml

Docker Registry v2.1

The Docker Registry release brings some major new features to the Docker
Registry along with numerous bug fixes, documentation enhancements and
logging improvements.  In total 203 issues were closed in 151 pull requests by
more than 50 contributors.

What’s new?

Support for listing Registry repositories
A specification and implementation of the catalog API allows users to list the
contents of their Registry

Manifest and Layer soft deletion
Manifests and layers can now be deleted by their reference.

Pull through caching (experimental)
The Registry can now act as a pull through cache, proxying content from the
Docker Hub.

Storage Drivers
The following storage drivers were contributed to the distribution project by
members of the open source community:

Aliyun OSS.   Open Storage Service (OSS) is a massive, secure and highly
reliable cloud storage service provided by Aliyun.

Ceph.  Ceph is a free software storage platform designed to present object,
block, and file storage from a single distributed computer cluster.

Openstack Swift.  Swift is a highly available, distributed, eventually
consistent object/blob store from Openstack.

And many more...
- API specification clarifications
- Etag support for layers and manifests
- htpasswd support with bcrypt
- Unix socket support
- Client disconnection detection
- A slimmer official image
- Faster push for multi-tagged images

v2.0.1: Minor release of Docker Registry 2.0

This release provides bug fixes, stability improvements,
better logging and extra documentation.

- Enable blob streaming upload
- S3 consistency checking and better resource utilization
- Eliminate resource leakage in the notification system
- Request error and storage driver logging
- Documentation corrections and additions

v2.0.0: Initial release of Docker Registry 2.0

First release of the new registry implementation. This provides an
implementation of the new Docker Registry HTTP API V2 for use with Docker 1.6+.
The new API and image manifest format provide faster and more secure image
distribution.

Please see the README for more information.

v2.0.0-rc.4: Optional resumable digest, logging adjustments, documentation

A build flag is now avialable to disable resumable digest support. This allows
installations that cannot use the forked crypto library to revert to using Go's
stdlib. Several fixes have been made to contextual logging output, including
ensuring accurate http response status, authorized user name and correct output
of the version.

The documentation continues to be shaped and massaged.

v2.0.0-rc.3: Driver tracing, documentation, and bugfixes

The main addition in this release candidate is around logging storage driver
calls with performance data and ensuring that log messages have nanosecond
granularity timestamps. Other bugfixes affect upload resource cleanup.

With this candidate, the documentation has undergone a large amount of
refactoring, including additions with various production setups.

v2.0.0-rc.2: Performance enhancements, bugfixes

This is an updated release candidate that includes a performance enhancement
for fetching manifest signatures. The backend path matching validity has been
relaxed to defer case-sensitive support to the storage backend.

v2.0.0-rc.1: Documentation, layer caching and bugfixes

This is an updated release candidate that includes layer info caching and some
bugfixes for cloudfront support. Documentation has also been heavily updated
but is still not complete.

v2.0.0-rc.0: Initial release candidate

This is the first release candidate for Registry 2.0. Since the alpha release,
we've mostly focused on hardening and refactoring to bring the software up to
production quality.