Cache Azure Container Registry Repositories about acr HOT 2 OPEN

here is one more use case, where limit of 50 rules won't work

problem: it may be hard to safely cleanup container registry, and in some cases registries are filled up quickly with tens of terabytes of images

idea:

imagine following setup:

• we have main.azurecr.io where each and every image published, it has quadrillion of images and weights tens of terabytes, it is hard to clean it up
• we have cache.azurecr.io side by side, configured as read only cache proxy against main.azurecr.io, all our Kubernetes clusters and other docker related services are talking to it

as result:

• it should be safe to remove images older than X months from main.azurecr.io
• it is still hard to cleanup cache.azurecr.io but it will be much smaller, because it holds only images used at least once
• cache.azurecr.io may be used to bypass limits from docker, quaye, etc.

why:

while playing with Azure Container Registry and connecting it, it took only 2 days to fill 50gb of data

when:

seems like limit of 50 rules is real blocker here, as a workaround we probably may have many registries, but it is error prone

alternative: of course, it will be much better to have idempotent builds and image tagging strategy that will override labels, but that's not always suitable

from acr.

It is annoying that you need to define a cache-rule for each and every repo - having a wildcard like docker.io/* mapping over to a prefix of docker.io/ within ACR would scale a lot better.

from acr.