From 98196ca95f58d2fc9da333d35f603202220c91c7 Mon Sep 17 00:00:00 2001 From: Craig Osterhout Date: Tue, 3 Feb 2026 12:44:31 -0800 Subject: [PATCH 1/2] hub: add deletion note Signed-off-by: Craig Osterhout --- .../docker-hub/repos/manage/hub-images/manage.md | 10 ++++++++-- content/reference/api/registry/latest.yaml | 8 ++++++++ 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/content/manuals/docker-hub/repos/manage/hub-images/manage.md b/content/manuals/docker-hub/repos/manage/hub-images/manage.md index f69c1cca9362..6b5427fadd89 100644 --- a/content/manuals/docker-hub/repos/manage/hub-images/manage.md +++ b/content/manuals/docker-hub/repos/manage/hub-images/manage.md @@ -26,6 +26,10 @@ The following objects are shown in the diagram. ## Manage repository images and image indexes +Use the following steps to delete one or more items via the graphical user +interface. To delete in bulk, see the [deletion API +endpoint](/reference/api/registry/latest/#tag/delete). + 1. Sign in to [Docker Hub](https://hub.docker.com). 2. Select **My Hub** > **Repositories**. 3. In the list, select a repository. @@ -51,7 +55,9 @@ The following objects are shown in the diagram. amount of storage you will reclaim. 4. Select **Delete forever**. - > [!NOTE] > - > If you would like to delete in bulk, you can use the [deletion API endpoint](/reference/api/registry/latest/#tag/delete). + > Deletion operations may take some time to complete. In rare cases, you may + > see a time-out error during the deletion process. If this occurs, the system will + > automatically retry the deletion in the background, and the items will be + > removed without requiring any action from you. diff --git a/content/reference/api/registry/latest.yaml b/content/reference/api/registry/latest.yaml index c38c9ffd718a..61e86fee82c0 100644 --- a/content/reference/api/registry/latest.yaml +++ b/content/reference/api/registry/latest.yaml @@ -200,6 +200,10 @@ tags: 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`. + > **Note** + > + > Manifest deletion operations may experience latency. In some cases, you may encounter 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. + This section outlines the basic steps to delete an image using the registry API. 1. [Get a bearer token for the repository](https://docs.docker.com/reference/api/registry/auth/). @@ -657,6 +661,10 @@ paths: 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`. This operation requires `delete` access to the repository. + + > **Note** + > + > Manifest deletion operations may take some time to complete. In some cases, you may receive a `500 Internal Server Error` response. If this occurs, the system will automatically retry the deletion in the background. The manifest will be removed without requiring manual intervention or additional requests from your side. parameters: - name: name in: path From 62d9ed7db463165ce0885f29b4330567889e5f64 Mon Sep 17 00:00:00 2001 From: Craig Osterhout Date: Thu, 5 Feb 2026 08:40:36 -0800 Subject: [PATCH 2/2] review1 Signed-off-by: Craig Osterhout --- .../manuals/docker-hub/repos/manage/hub-images/manage.md | 8 ++++---- content/reference/api/registry/latest.yaml | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/manuals/docker-hub/repos/manage/hub-images/manage.md b/content/manuals/docker-hub/repos/manage/hub-images/manage.md index 6b5427fadd89..b0744339dcf3 100644 --- a/content/manuals/docker-hub/repos/manage/hub-images/manage.md +++ b/content/manuals/docker-hub/repos/manage/hub-images/manage.md @@ -57,7 +57,7 @@ endpoint](/reference/api/registry/latest/#tag/delete). > [!NOTE] > - > Deletion operations may take some time to complete. In rare cases, you may - > see a time-out error during the deletion process. If this occurs, the system will - > automatically retry the deletion in the background, and the items will be - > removed without requiring any action from you. + > Deletion operations may take some time to complete. Timeout errors may + > occur during the deletion process. The system automatically retries the + > deletion in the background, and the items will be removed without requiring + > any action from you. \ No newline at end of file diff --git a/content/reference/api/registry/latest.yaml b/content/reference/api/registry/latest.yaml index 61e86fee82c0..445cc7f98f95 100644 --- a/content/reference/api/registry/latest.yaml +++ b/content/reference/api/registry/latest.yaml @@ -202,7 +202,7 @@ tags: > **Note** > - > Manifest deletion operations may experience latency. In some cases, you may encounter 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. + > 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. This section outlines the basic steps to delete an image using the registry API. @@ -664,7 +664,7 @@ paths: > **Note** > - > Manifest deletion operations may take some time to complete. In some cases, you may receive a `500 Internal Server Error` response. If this occurs, the system will automatically retry the deletion in the background. The manifest will be removed without requiring manual intervention or additional requests from your side. + > 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. parameters: - name: name in: path