4 ms·
I guess CI services like Github Actions could be easily hitting these limits (100 pulls per IP per 6 hours).
by jpalomaki 6y ago
I guess CI services like Github Actions could be easily hitting these limits (100 pulls per IP per 6 hours).
- eblanshey 6y agoI'm thinking the same thing. GitLab has shared CI runners that probably do a lot of image pulling. Hopefully they have plans to implement their own docker registry cache.
- tr-gitlab 6y agoGitLab PM here - we have a feature called the [Dependency Proxy](https://docs.gitlab.com/ee/user/packages/dependency_proxy/ https://docs.gitlab.com/ee/user/packages/dependency_proxy/) that allows you to cache images from DockerHub. Currently this only works for public projects, but we are working on adding support for private projects now: https://gitlab.com/gitlab-org/gitlab/-/issues/11582 https://gitlab.com/gitlab-org/gitlab/-/issues/11582.
- lights0123 6y agoI would imagine that GitHub would work out something with Docker to either pay themselves or have some way of caching images themselves. They could just inject their own TLS certificates into their VMs and then intercept Docker requests for images with their own cache.
- jacques_chester 6y agoI am anecdotally aware of large Concourse installations that have caused individual companies to be blocked entirely from Dockerhub (and which caused "face melting" of Github Enterprise instances). Badly-behaved CI is a serious issue at scale.