Quotas for Container registry

How many repositories, cache rules and signing keys your organization can have, how much it can store, and how to raise a quota.

Last updated 18 November 2026View as Markdown
QuotaDescriptionDefaultTrialApplies toAdjustable
RepositoriesContainer repositories, including pull-through cache repositories1.00050OrganizationYes
Registry storageBytes of the organization’s image layers, each layer counted once however many repositories use it. Expired images waiting to be purged do not count.214.748.364.80010.737.418.240OrganizationYes
Pull-through cache rulesUpstream registries mirrored under a prefix505OrganizationYes
Signing keysTrusted cosign keys and notation certificates205OrganizationYes

Generated from the quota descriptors: the numbers are the ones the API enforces.

  • Repositories include pull-through cache repositories. A create over the quota is refused with 409 and code QuotaExceeded; a docker push that would create a repository over it is refused with DENIED and the same message, which starts with "Quota exceeded:".
  • Registry storage counts the layers in repositories, each once; layers held only by expired images do not count. You can also set a lower cap of your own (see Set a storage quota).

Fixed limits

These are not quotas and cannot be raised.

What Limit
Manifest 4 MiB
Tag patterns that stay mutable 10 per repository
Lifecycle rules 50 per policy
Registry aliases 20

Raise a quota

This needs quotas:ListServiceQuotas to open the page (without it the page shows only a refusal) and quotas:RequestServiceQuotaIncrease.

  1. Open Service quotas in the Deutsche Cloud Console.
  2. On the quota's row, open its action menu and choose Request increase. It is not offered while a request for the quota is still open.
  3. For New value (New value (GiB) for Registry storage), enter a value above the current one, up to the quota's ceiling.
  4. For What you need it for, enter the reason (at least 10 characters), then choose Send request.

On a standard organization, a request for Repositories, Pull-through cache rules or Signing keys up to twice the standard default is approved at once, unless one was approved that way recently; any other request, including every Registry storage request, is decided by Deutsche Cloud staff, and you get an event when they decide.

On a trial organization the message says to ask Deutsche Cloud support to move it to standard quotas.

Did this page help you?