Open ElieAzar-Algo opened 3 weeks ago
can you try to restart harbor? and then check the storage again.
Thank you, @wy65701436, for your response.
I restarted Harbor, but the storage issue persists. In fact, we've done multiple restarts over the past few days without any improvement.
Expected behavior and actual behavior:
I encountered a problem with the cleanup of unused Docker images due to full storage on my server.
Expected Behavior:
The mounted storage pointing to the Docker Images directory is full:
To free up space, I applied the following retention policy to the project with approximately 125GB of images:
After running the retention policy, I observed the following result in the UI:
Next, I went to the "Clean Up" section, ran the Garbage Collection, and received this output:
The expected result was for the images to be cleaned up and the storage to reflect something around the following:
Actual Behavior:
However, the actual result is that the Garbage Collection only freed up about 10GB of space, despite the UI indicating that 15710 blob(s) and 5974 manifest(s) were deleted, freeing up 120.57GiB, as shown in the screenshot above.
Steps to reproduce the problem:
Confirm that the storage mounted on the server for Docker images is full:
Go to the project in Harbor with the highest size of Docker images.
Apply the following retention policy:
**
, retain the most recently pushed 5 artifacts with tags matching**
, and include untagged artifacts.Run the retention policy and observe the result in the UI. as shown above in the screenshot that everything is going as expected
Go to the "Clean Up" section and run the Garbage Collection with the following settings:
Note the output that shows the following:
Check the server storage again using the
df -h
command:Versions:
Please specify the versions of following systems.
Additional context:
Harbor config files: