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
<!--Delete sections as needed -->
## Description
Delete operation may time-out. Hub automatically retries without user
interaction in both the UI and API.
Added notes to make the user aware.
## Related issues or tickets
ENGDOCS-3173
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
Copy file name to clipboardExpand all lines: content/reference/api/registry/latest.yaml
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -200,6 +200,10 @@ tags:
200
200
201
201
Only untagged manifests (or those not referenced by other tags or images) can be deleted. If a manifest is still referenced, the registry returns `403 Forbidden`.
202
202
203
+
> **Note**
204
+
>
205
+
> Manifest deletion operations may experience latency and could return a `500 Internal Server Error` during deletion. The system automatically retries the deletion in the background, so the manifest will eventually be removed. You do not need to manually retry the request.
206
+
203
207
This section outlines the basic steps to delete an image using the registry API.
204
208
205
209
1. [Get a bearer token for the repository](https://docs.docker.com/reference/api/registry/auth/).
@@ -657,6 +661,10 @@ paths:
657
661
Only untagged or unreferenced manifests can be deleted. If the manifest is still referenced by a tag or another image, the registry will return `403 Forbidden`.
658
662
659
663
This operation requires `delete` access to the repository.
664
+
665
+
> **Note**
666
+
>
667
+
> Manifest deletion operations may take some time and could return a `500 Internal Server Error`. The system automatically retries the deletion in the background. Manual intervention is not required.
0 commit comments