Following the idea in (DockerHub) Proxy Cache , we deployed a self-hosted Harbor instance at cr.codefloe.com.
Within this instance, we configured proxy caches to docker.io (DockerHub) and ghcr.io (Github Container Registry). Proxy caches pull images centrally and serve them from a cached store, effectively avoiding running into rate limits for the respective upstream registries.
While users can also define registry credentials in Crow directly, this provides a central convenient option within CodeFloe CI for this problem. Both Forgejo Actions and Crow CI can use the proxy cache.
To avoid abuse, the proxy cache is only usable from CodeFloe-owned servers. If you have deployed your own runners and want them to be allowlisted, please reach out to us!
Read more about the proxy cache in our docs.