centersl/docker-docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-03-27 06:18:55 +07:00
Code Issues Packages Projects Releases Wiki Activity

hub: add deletion note (#24078)

Browse Source 
<!--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>
This commit is contained in:
Craig Osterhout
2026-02-18 14:56:52 -08:00
committed by GitHub
parent cecdc28d1d
commit 4cae670c4d
2 changed files with 16 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
content/manuals/docker-hub/repos/manage/hub-images/manage.md
View File

@@ -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. 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.

8
content/reference/api/registry/latest.yaml
View File

@@ -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 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.
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 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