I have images in my registry showing around 2.5GB of images but registry showing limit exceed. Ran GC alot of time but still no resolution.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Sometimes the registry usage shown in the dashboard can lag behind actual usage, especially after deleting images or running garbage collection.
If you’ve already run GC multiple times and the limit still looks incorrect, it might be worth opening a support ticket so the team can check the backend usage for your registry and see what’s going on:
Hi,
Sometimes there are untagged manifests and orphaned blob layers eating up space that GC doesn’t touch by default.
When you run GC, make sure you’re using:
doctl registry garbage-collection start --include-untagged-manifests
Without --include-untagged-manifests, GC only cleans up layers that aren’t referenced by any manifest — but old untagged manifests themselves stick around and so do their layers.
Regards
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.