Registry limitations

Container registry is subject to the following limits and quotas

Images must follow a repo/image format

All images stored in registry must have a ‘repo’. This is just a prefix path.

E.g. to store the popular alpine image, you may wish to add it into an oss/ repo.

That would then be YOUR_SUBDOMAIN.ctr.dev/oss/alpine.

Multiple images can be contained in the same repo, so a single registry with oss/alpine and oss/ubuntu is supported.

Repos can be useful if you want to share collections of images with groups of users e.g. mycustomer/backend & mycustomer/frontend could be shared with a single role granting pull on mycustomer/*.

5GB maximum layer size

Whilst images of any size are supported, the maximum size for an individual layer in an image is currently 5GB. This limit will not impact the vast majority of images, though we plan to support arbitrary layer sizes in the near future.

Storage cap dependent on plan

Storage limits are shared across all projects/registries within an account and are dependent on your tier.

Enterprise tier storage can be customised to your needs as part of onboarding.