Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache Azure Container Registry Repositories #689

Open
JXavierMSFT opened this issue Apr 12, 2023 · 7 comments
Open

Cache Azure Container Registry Repositories #689

JXavierMSFT opened this issue Apr 12, 2023 · 7 comments

Comments

@JXavierMSFT
Copy link

JXavierMSFT commented Apr 12, 2023

Caching for ACR will soon allow users to cache repositories from other Azure Container Registries. This functionality is tentatively scheduled for release in late December 2023.

@mac2000
Copy link

mac2000 commented Jul 12, 2023

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

image

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

@davidkarlsen
Copy link

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.

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@sajayantony
Copy link
Contributor

@JXavierMSFT do we have any updates on prefix matching.

@JXavierMSFT
Copy link
Author

We have released Wildcard cache rules. You can check the docs at aka.ms/acr/cache. However, we haven't released Azure Container Registry as an upstream yet. I will update this thread as soon as we release.

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@floriankoch
Copy link

@JXavierMSFT anything new for caching ACR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

5 participants