Docker Registry v2.4.0-rc.0

What's new?

New S3 storage driver
Garbage collector command
Manifest events include tag
Relative URLs in HTTP headers and events
v1 signatures can be generated.

Gotchas

The RADOS storage driver has been removed.
The command line format has changed to support subcommands. To run a registry as before an additional subcommand - serve - is required.
The legacy S3 storage driver, based on adroll/goamz is now deprecated and will be removed in a future release.

Docker Registry v2.3.1

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.1-rc.0

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 the Manifest Schema 2 specification

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: #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 the compatibility documentation

Docker Registry v2.3.0-rc.2

Invalidate the blob store descriptor cache when removing proxied content.

Docker Registry v2.3.0-rc.1

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

Docker Registry v2.3.0-rc.0

Fixes a bug where the incorrect content type for Schema 1 manifests was
returned.

This release candidate is not compatible with docker engine v1.10.0-rc1

Docker Registry v2.3.0 alpha

This is an alpha release of the Docker Registry v2.3

This is the first Registry release to support multiple-architecture manifests and cross repository blob mounting

Do not deploy this in production.

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.

Notable Changes

Storage Drivers correctly handle empty directories.

Swift storage driver support for bulk deletes and improved handling of eventually
consistent configurations.

Reduction in roundtrips for layer download.

Catalog performance improvements.

Docker Registry 2.2.0

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.