Reply to post: Re: Caching?

Ready for pull rate limits? Docker outlines 'next chapter' as Google tells customers how to dodge subscriptions

MatthewSt Silver badge

Re: Caching?

Because the images have a hash based on their contents it doesn't matter _where_ you pull them down from as long as you've validated the hash. They're effectively signed (unless there's a weakness/collision discovered).

On the flip side of this, they should be the easiest thing in the world to cache, because you're downloading them based on a request that indicates the contents that you want to download. The image for a particular hash will _never_ change, so your caching can be based off LRU and you're sorted.

Even Microsoft have worked out how to do this, and their build agents have a certain number of popular images cached _on the build server itself_.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Biting the hand that feeds IT © 1998–2021