|
46 | 46 | Specifies registry authentication. |
47 | 47 | externalDocs: |
48 | 48 | description: Detailed authentication workflow and token usage |
49 | | - url: /reference/api/registry/auth/ |
| 49 | + url: https://docs.docker.com/reference/api/registry/auth/ |
50 | 50 |
|
51 | 51 | - name: Manifests |
52 | 52 | x-displayName: Manifests |
|
64 | 64 | description: | |
65 | 65 | Pulling an image involves retrieving the manifest and downloading each of the image's layer blobs. This section outlines the general steps followed by a working example. |
66 | 66 |
|
67 | | - 1. [Get a bearer token for the repository](/reference/api/registry/auth/). |
| 67 | + 1. [Get a bearer token for the repository](https://docs.docker.com/reference/api/registry/auth/). |
68 | 68 | 2. [Get the image manifest](#operation/GetImageManifest). |
69 | 69 | 3. If the response in the previous step is a multi-architecture manifest list, you must do the following: |
70 | 70 | - Parse the `manifests[]` array to locate the digest for your target platform (e.g., `linux/amd64`). |
@@ -115,7 +115,7 @@ tags: |
115 | 115 | |
116 | 116 | This section outlines the basic steps to push an image using the registry API. |
117 | 117 |
|
118 | | - 1. [Get a bearer token for the repository](/reference/api/registry/auth/) |
| 118 | + 1. [Get a bearer token for the repository](https://docs.docker.com/reference/api/registry/auth/) |
119 | 119 |
|
120 | 120 | 2. [Check if the blob exists](#operation/CheckBlobExists) using a `HEAD` request for each blob digest. |
121 | 121 |
|
@@ -202,7 +202,7 @@ tags: |
202 | 202 |
|
203 | 203 | This section outlines the basic steps to delete an image using the registry API. |
204 | 204 |
|
205 | | - 1. [Get a bearer token for the repository](/reference/api/registry/auth/). |
| 205 | + 1. [Get a bearer token for the repository](https://docs.docker.com/reference/api/registry/auth/). |
206 | 206 | 2. [Get the manifest](#operation=GetImageManifest) using the image's tag. |
207 | 207 | 3. Retrieve the `Docker-Content-Digest` header from the manifest response. This digest uniquely identifies the manifest. |
208 | 208 | 4. [Delete the manifest](#operation=DeleteImageManifest) using a `DELETE` request and the digest. |
|
0 commit comments