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
Currently the only way to delete repository from registry is by deleting it's directory manually from registry-v2/docker/registry/v2/repositories directory in storage. Until then the repo will be returned by catalog API and cause confusion when people delete manifests and tags from the repo. See #2434. There should be API to delete repo DELETE /v2/<repo> and delete tag DELETE /v2/<repo>/tags/<tagname>. These API implementations will effectively remove the repo directory from registry-v2/docker/registry/v2/repositories and tag directory from registry-v2/docker/registry/v2/repositories/<repo>/tags correspondingly.
The text was updated successfully, but these errors were encountered:
Whenever we've removed all tags for a repository, the repository will still
show up in the catalog because of an open bug
distribution/distribution#2747
and the tags/list endpoint would return 404. So handle that situation without
throwing an exception - just return an empty tags list.
Bug: T242604
Change-Id: Ie3d8f20fd74224f2d926133c17c4c7d396358028
Currently the only way to delete repository from registry is by deleting it's directory manually from
registry-v2/docker/registry/v2/repositories
directory in storage. Until then the repo will be returned by catalog API and cause confusion when people delete manifests and tags from the repo. See #2434. There should be API to delete repoDELETE /v2/<repo>
and delete tagDELETE /v2/<repo>/tags/<tagname>
. These API implementations will effectively remove the repo directory fromregistry-v2/docker/registry/v2/repositories
and tag directory fromregistry-v2/docker/registry/v2/repositories/<repo>/tags
correspondingly.The text was updated successfully, but these errors were encountered: