4 ms·
I would not recommend doing it through Docker, though, especially after this change. We use AWS's ECR, and you can set it to do pull-through caching of public i
by the_jeremy 4y ago
I would not recommend doing it through Docker, though, especially after this change. We use AWS's ECR, and you can set it to do pull-through caching of public images, so images you've already used will stick around even if Docker blows up, and you don't have to pull the images yourself, you just point everything in your environment to ECR and ~~ECR will pull from docker hub~~ (EDIT: it only supports quay.io, not docker hub) and start building its cache as you use the images.
- dbingham 4y agoKnowing ECR has pull through caching is really helpful. I'm sure we would have come across that in the course of investigating our response, but this definitely saved us some time! Edit: Damn, looks like ECR's pull through caching only works for ECR Public and Quay? It's a little unclear, but maybe not a drop in solution for Docker Hub replacement. https://docs.aws.amazon.com/AmazonECR/latest/userguide/pull-through-cache.html https://docs.aws.amazon.com/AmazonECR/latest/userguide/pull-...
- wavesquid 4y agoECR pull through caching is only possible for other ECR repos or quay.io. you cannot use it for Docker hub.
- the_jeremy 4y agoah, sorry. We only use it for quay, I didn't realize that was out of necessity rather than targeting.