-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Publish images to alternative registry #1133
Comments
you can always make your own registry and pull/push images there. |
Yep, that's what we're currently doing -- we just copied images over into our own registry. That being said, it's just another point of friction for new users, so in an ideal world we lower the bar to entry for anyone. |
@anishasthana Do you have any recommendation for this issue? Thanks! |
My recommendation would be:
I'm happy to assist on any of this -- I'm quite familiar with quay. |
@kevin85421 Can anyscale offer some premium plans for dockerhub kuberay? or just host kuberay under dockerhub ray-project? |
The issue would be on the pulling side -- anyone wanting to pull images would also need a premium plan with dockerhub to not be rate-limited. |
Thank you, @anishasthana, for the insightful suggestion! We will discuss this internally to determine if there is an existing solution in Ray or not, and we will get back to you as soon as possible. |
This issue can be closed by #1307. Thank @anishasthana for the guidance! The next step is to update the doc and may be change the default image registry to |
Search before asking
Description
DockerHub allows you to pull only 100 images per 6 hour window[1], which isn't a lot. This results in the following error occurring fairly frequently.
There are other container registries such as quay.io we could push images to instead (or as well) so as to get around the rate limit issues.
[1] https://docs.docker.com/docker-hub/download-rate-limit/
Use case
Reduce instances of rate limit errors when pulling images from DockerHub.
Related issues
#829
opendatahub-io/distributed-workloads#47
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: