Fix broken link, remove incorrect CLI link

This commit is contained in:
Maria Bermudez 2019-02-01 16:18:47 -08:00 committed by GitHub
parent d7c32065fb
commit e59c329e53
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -10,9 +10,9 @@ This document outlines the functionalities or components within DTR that will be
#### 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.
Since `v2.5`, it has been possible for repository admins to autogenerate manifest lists when [creating a repository via the API](/datacenter/dtr/2.5/reference/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/).
The above behavior and the `enableManifestLists` field will be removed in `v2.7`. Starting in `v2.7`, you can use the CLI to create and push a manifest list to any repository.