Report this

What is the reason for this report?

Registry showing wrong limit

Posted on March 2, 2026

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!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

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:

https://do.co/support

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

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Dark mode is coming soon.