ef8966aacd
Restore the documentation that was moved to https://github.com/docker/docker.github.io Conflicts: docs/compatibility.md docs/deploying.md docs/deprecated.md docs/garbage-collection.md docs/glossary.md docs/help.md docs/images/notifications.png docs/index.md docs/insecure.md docs/introduction.md docs/migration.md docs/notifications.md docs/recipes/apache.md docs/recipes/index.md docs/recipes/mirror.md docs/recipes/nginx.md docs/recipes/osx-setup-guide.md docs/recipes/osx/config.yml docs/storage-drivers/azure.md docs/storage-drivers/filesystem.md docs/storage-drivers/gcs.md docs/storage-drivers/index.md docs/storage-drivers/inmemory.md docs/storage-drivers/oss.md docs/storage-drivers/s3.md docs/storage-drivers/swift.md
22 lines
814 B
Markdown
22 lines
814 B
Markdown
---
|
|
description: describes deprecated functionality
|
|
keywords: registry, manifest, images, signatures, repository, distribution, digest
|
|
title: Docker Registry deprecation
|
|
---
|
|
|
|
{% include registry.md %}
|
|
|
|
This document details functionality or components which are deprecated within
|
|
the registry.
|
|
|
|
### v2.5.0
|
|
|
|
The signature store has been removed from the registry. Since `v2.4.0` it has
|
|
been possible to configure the registry to generate manifest signatures rather
|
|
than load them from storage. In this version of the registry this becomes
|
|
the default behavior. Signatures which are attached to manifests on put are
|
|
not stored in the registry. This does not alter the functional behavior of
|
|
the registry.
|
|
|
|
Old signatures blobs can be removed from the registry storage by running the
|
|
garbage-collect subcommand.
|