Creating this as a placeholder based on discussion in Slack and yesterday's SIG Testing meeting. I'll sketch in what I remember but to defer to @BenTheElder for a plan
Dockerhub is going to rate-limit pulls starting Nov 1st. See https://www.docker.com/pricing/resource-consumption-updates
A pull request is up to two GET requests to the registry URL path ‘/v2//manifests/’. [...] Note that all pull requests, including ones for images you already have, are counted by this method. This is the trade-off for not counting individual layers.
Rate limits for Docker image pulls are based on the account type of the user requesting the image - not the account type of the image’s owner.
Because we are limiting on manifest requests, the number of layers (blob requests) related to a pull is unlimited at this time.
Please see https://docs.docker.com/registry/recipes/mirror/ to run docker/distribution as a mirror
Pull limit is:
Ideas:
We will likely need to fan out audit/change jobs to all SIGs / subprojects.
I think to start with we should ensure merge-blocking kubernetes/kubernetes jobs are safe, since they represent significant CI volume
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4