mirror of https://github.com/docker/docs.git
Merge pull request #798 from docker/deprecation-notice
Document planned deprecation of current ManifestLists behavior
This commit is contained in:
commit
9c730c3b40
|
@ -0,0 +1,18 @@
|
|||
---
|
||||
description: Page for deprecation announcements.
|
||||
keywords: registry, manifest, images, signatures, repository, distribution, digest
|
||||
title: Deprecation Notice
|
||||
---
|
||||
|
||||
This document outlines the functionalities or components within DTR that will be deprecated.
|
||||
|
||||
### Enable Manifest List via the API
|
||||
|
||||
#### 2.5 and 2.6
|
||||
|
||||
Since `v2.5`, it has been possible for repository admins to autogenerate manifest lists when [creating a repository via the API](./reference/dtr/2.5/api/). You accomplish this by setting `enableManifestLists` to `true` when sending a POST request to the `/api/v0/repositories/{namespace}` endpoint. When enabled for a repository, any image that you push to an existing tag will be appended to the list of manifests for that tag. `enableManifestLists` is set to false by default, which means pushing a new image to an existing tag will overwrite the manifest entry for that tag.
|
||||
|
||||
#### 2.7
|
||||
|
||||
The above behavior and the `enableManifestLists` field will be removed in `v2.7`. Starting in `v2.7`, you can use the CLI command, `docker manifest`, to [create and push a manifest list to any repository](./engine/reference/commandline/manifest/).
|
||||
|
Loading…
Reference in New Issue