Describe the solution you'd like
Since Docker Hub has now rate limits, it would be great if images are moved somewhere else.
Describe alternatives you've considered
Proxying or mirroring docker hub images.
Additional context
Add any other context or screenshots about the feature request here.
Hello @aelbarkani
In the meantime, here is a solution that can help resolve the rate limiting problem temporarily:
docker login and push them to an internal registry.Thanks for the workaround @balaramesh. Any timeline of when it is expected to move the images out of Docker Hub ?
Hi @aelbarkani,
We don't have a date for moving the images out of Docker Hub at this time.
Please do not remove images from Docker Hub, it works well and does not require new firewall rules who allow it (those who don't usually upload container images to private registry).
Wouldnt it be possible to "just" publish them to a secondary Location like quay.io or something owned from netapp.
This is stupid rate limiter has already killed my trident updates multiple times as durring the update the container is pulled from docker.io. Also syncing it to the internal (in my case openshift) registry doesnt work due to the poll limit.
I would be really happy to have them on some other registry just not docker.io .
BR and keep up the great work :) !
Mirroring the image to Quay would make sense in my opinion. We have been hitting this issue also, but it is the only cluster operator we are using that comes from Docker Hub since we are using OpenShift. Is there an easy way to change Trident to use an image from the local registry post install?
+1 For mirroring the images on quay.io (or other), rate limiting is affecting Trident updates.
Most helpful comment
Mirroring the image to Quay would make sense in my opinion. We have been hitting this issue also, but it is the only cluster operator we are using that comes from Docker Hub since we are using OpenShift. Is there an easy way to change Trident to use an image from the local registry post install?