29 ms·
It sounds like it definitely does trigger the rate limiter. > There is a small tradeoff – if you pull an image you already have, this is still counted even if
by nrmitchi 6y ago
It sounds like it definitely does trigger the rate limiter.
> There is a small tradeoff – if you pull an image you already have, this is still counted even if you don’t download the layers.
I expect we're just going to see a lot more recycling of build nodes once it has "used up it's docker credits".
- heavenlyblue 6y agoAll reasonable orgs should have had their private docker repo a long time ago. Everybody else is living the pipe dream where they have externalised their risk and probably deserve the Docker treatment.
- jhenkens 6y agoAgreed. Third party package repositories has been a weak point in our CI, and we put all of them behind a self-hosted proxy that we can manage in our own HA fasion. Turns out we get faster pulls from it, as well as being a good internet-citizen.
- Spivak 6y agoYes but Docker achieved their goal of making it annoying as hell to not user DockerHub. Because you can run your own private repo just fine but what you want is a transparent proxy (like apt-catcher) that will let you pretend you’re using DH but actually pulling from either the cache or your private repos. All the pieces are there with private repos and “pullthrough” proxies they’re just not well integrated, seemingly on purpose. RedHat’s patches to Docker make this possible but Docker has refused to upstream it.
- heavenlyblue 6y ago> annoying as hell to not user DockerHub Why? All your need to do is to use your domain name when referencing the image.