Skip to content

Commit 4cae670

Browse files
hub: add deletion note (#24078)
<!--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>
1 parent cecdc28 commit 4cae670

2 files changed

Lines changed: 16 additions & 2 deletions

File tree

content/manuals/docker-hub/repos/manage/hub-images/manage.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,10 @@ The following objects are shown in the diagram.
2626

2727
## Manage repository images and image indexes
2828

29+
Use the following steps to delete one or more items via the graphical user
30+
interface. To delete in bulk, see the [deletion API
31+
endpoint](/reference/api/registry/latest/#tag/delete).
32+
2933
1. Sign in to [Docker Hub](https://hub.docker.com).
3034
2. Select **My Hub** > **Repositories**.
3135
3. In the list, select a repository.
@@ -51,7 +55,9 @@ The following objects are shown in the diagram.
5155
amount of storage you will reclaim.
5256
4. Select **Delete forever**.
5357

54-
5558
> [!NOTE]
5659
>
57-
> If you would like to delete in bulk, you can use the [deletion API endpoint](/reference/api/registry/latest/#tag/delete).
60+
> Deletion operations may take some time to complete. Timeout errors may
61+
> occur during the deletion process. The system automatically retries the
62+
> deletion in the background, and the items will be removed without requiring
63+
> any action from you.

content/reference/api/registry/latest.yaml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -200,6 +200,10 @@ tags:
200200
201201
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`.
202202
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+
203207
This section outlines the basic steps to delete an image using the registry API.
204208
205209
1. [Get a bearer token for the repository](https://docs.docker.com/reference/api/registry/auth/).
@@ -657,6 +661,10 @@ paths:
657661
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`.
658662
659663
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.
660668
parameters:
661669
- name: name
662670
in: path

0 commit comments

Comments
 (0)