News for hackers. Stuff that matters.
Re:Docker to rate limit image pulls by mikepurvis on Monday August 24, 2020 @02:09PM (#24263521)
No they don't, but if you do something silly like spin up a bare VM build node, and then pull your environment every time, then obviously you won't get any caching.
Re:Docker to rate limit image pulls by ArchOversight on Monday August 24, 2020 @02:26PM (#24263731)
Github Actions? Gitlab CI? Many of those don't do any caching because of the chance of poisoning a tag in the local registry, and don't have a good way to do caching per project.

I can imagine that this affects those sorts of operations.

Re:Docker to rate limit image pulls by throwanem on Monday August 24, 2020 @02:55PM (#24264066)
Yeah, that's what I was getting at - in CI I can see it, but in local dev it would seem surprising to need more than the free-with-authentication quota.

That said, if your CI needs more, it's probably time to invest in a paid account if you can, and certainly if you're commercial.

Re:Docker to rate limit image pulls by tr-gitlab on Monday August 24, 2020 @06:01PM (#24266050)
You can use the GitLab Dependency Proxy for caching images from DockerHub, it's pretty straightforward to pull cached images:

https://docs.gitlab.com/ee/user/packages/dependency_proxy/

Re:Docker to rate limit image pulls by atomi on Monday August 24, 2020 @03:34PM (#24264532)
Using `docker-machine` You can use an environment variable to pull from a local docker mirror from new bare VMs.

`export ENGINE_REGISTRY_MIRROR=https://mirror.mysite.com`