Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/storage/docker/registry/v2/repository has not been deleted when gc & purge policy #21690

Open
Jim0530 opened this issue Mar 4, 2025 · 0 comments

Comments

@Jim0530
Copy link

Jim0530 commented Mar 4, 2025

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:

I have configured a policy for every project to retain artifacts pushed within the last 3 days, with tags matching **, including untagged artifacts. However, the storage is still full. Upon inspecting the /storage folder, I found that while the /storage/docker/registry/v2/blob directory is being correctly purged, both ui and the result of du -h blobs are equal.
The /storage/docker/registry/v2/repository directory still contains data from repositories that have already been deleted and no longer appear in the UI.

Steps to reproduce the problem:

Versions:
Harbor ==> v2.12.0-9da38ae0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants