You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: spec.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -365,7 +365,7 @@ The `name` and `reference` parameter identify the image and are required.
365
365
The reference may include a tag or digest.
366
366
367
367
The client should include an Accept header indicating which manifest content types it supports.
368
-
For more details on the manifest formats and their content types, see [manifest-v2-1.md](manifest-v2-1.md) and [manifest-v2-2.md](manifest-v2-2.md).
368
+
For more details on the manifest formats and their content types, see [manifest-v2-1.md](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-1.md) and [manifest-v2-2.md](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md).
369
369
In a successful response, the Content-Type header will indicate which manifest type is being returned.
370
370
371
371
A `404 Not Found` response will be returned if the image is unknown to the registry.
@@ -935,7 +935,7 @@ If the image had already been deleted or did not exist, a `404 Not Found` respon
0 commit comments