Hacker News Reader

I 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.

I'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.

GitLab PM here - we have a feature called the [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.

I 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.