News for hackers. Stuff that matters.

A comment on Docker limits unauthenticated pulls to 10/HR/IP from Docker Hub, from March 1.

Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by keisborg on Friday February 21, 2025 @05:27AM (#43125986)
It is not immediately clear to me if the limit is per repo/package or globally in the hub. For instance, I fear it will not be possible to add a new kubernetes node to my cluster without hitting the limit as it would need to pull all the individual images.
[ Parent | on HN ]
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by ragingroosevelt on Friday February 21, 2025 @05:33AM (#43126030)
Why are you not using a registry mirror/cache (eg jfrog artifactory, etc)? Own your supply chain.
[ Parent | on HN ]
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by RobotToaster on Friday February 21, 2025 @05:40AM (#43126069)
When that cache has to update it will make more than 10 pulls.
[ Parent | on HN ]
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by keisborg on Friday February 21, 2025 @06:05AM (#43126246)
Exactly this. And when a base image has a new release, all images based on this will also need an update
[ Parent | on HN ]
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by davman on Friday February 21, 2025 @11:18AM (#43129290)
its globally in the hub. The announcement says they are rolling out the block in March but this already blew up my k8s clusters since last weekend. Have tried looking for an option to tell k8s to always use authentication tokens for image pulls, but can't find a way, going to have to add Kyverno to mutate all incoming Deployments to add imagePullSecrets.
[ Parent | on HN ]