Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock...
by kennysoona on Friday February 21, 2025 @05:14AM
(#43125921)
Medium to large orgaizations probably should have been caching images anyway out of courtesy.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock...
by theshrike79 on Friday February 21, 2025 @06:53AM
(#43126495)
It's not simple, you need to modify every Dockerfile and compose.yml to point to your cache instead of just using it directly.
Still doable though.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock...
by Reubensson on Friday February 21, 2025 @09:03AM
(#43127531)
With podman and kube (crio and containerd) you can create mirror config such that the pulls happen from a mirror transparently. Some mirrors also support proxy cache behaviour so you dont in theory have to preload images (though might be necessary with the new limits)
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock...
by Spivak on Friday February 21, 2025 @10:32AM
(#43128608)
Docker Inc. pushed all this work on individuals by being shitty and not supporting adding the ability to add to / change the default registry search. Redhat has been patching Docker engine to let their users do it. It would be trivial if it could be an engine-wide setting ["mydockercache.me", "docker.io"] that would be transparent to everyone's Dockerfile.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock...
by xena on Friday February 21, 2025 @11:08AM
(#43129143)
There is, add this to your /etc/docker/daemon.json:
{
"registry-mirrors": [
"https://pt-dh.int.xeserv.us"
]
}
Where the URL points to your pull-through docker hub cache.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock...
by unhingedlife on Friday February 21, 2025 @12:01PM
(#43129953)
None of this is simple. Fortunately, we're experts whose job it is to do this kind of work. People! You are not helpless!
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock...
by doublerabbit on Friday February 21, 2025 @05:14AM
(#43125923)
Exactly what they want.
This forces pretty much everyone to move to a Pro subscription or to put a cache in front of docker.io.