You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Closing this, the culprit image is docker.io/library/registry:2. Plus, by being on the rancher DockerHub namespace, it should not be rate limited already.
Hi,
When installing k3d on CI for kubewarden/kubewarden-end-to-end-tests, k3s of course gets pulled from DockerHub. This means that users get rate-limited.
As an open source project, K3s may benefit from letting its users do pulls of the images without rating, by just applying to https://www.docker.com/community/open-source/application.
Note the qualifications (which I think k3s passes), and that it may need to move to a different DockerHub namespace.
Alternatives
Release images in ghcr.io for downstream consumers such as k3d.
The text was updated successfully, but these errors were encountered: