3 ms·
10 pulls an hour is wild. There's no way we can wait hours and hours for work clusters to rebuild. Even just daily updates to containers will be over 10. This
by crimsonnoodle58 2y ago
10 pulls an hour is wild. There's no way we can wait hours and hours for work clusters to rebuild. Even just daily updates to containers will be over 10.
This forces pretty much everyone to move to a Pro subscription or to put a cache in front of docker.io.
- kennysoona 2y agoMedium to large orgaizations probably should have been caching images anyway out of courtesy.
- theshrike79 2y agoIt'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.
- Reubensson 2y agoWith 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)
- Spivak 2y agoDocker 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.
- xena 2y agoThere 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.
- unhingedlife 2y agoNone of this is simple. Fortunately, we're experts whose job it is to do this kind of work. People! You are not helpless!
- doublerabbit 2y agoExactly what they want.
- baq 2y agoYou should have a cache anyway and yes it's crazy a business would want money for a service, oh wait
- lemper 2y agoyes. paying for service should not be controversial, no?
- deleted 2y ago[deleted]