-
-
Notifications
You must be signed in to change notification settings - Fork 486
Publish to Github's Package repo in response to Dockerhub's new rate limits #1282
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
Comments
Thanks for asking. Currently nothing is being planned but will take some time to evaluate this. |
@ShreyasZare Hi and thank you for the gr amazing job. |
@Delta1977 Thanks for the feedback. Just trying to understand how the rate limit is being implemented. The docs say that limit is 100 pulls/6hrs for unauthenticated users. I am not sure how you got affected by this but do let me know about it. |
He was probably affected by this because he pulled more than 100 containers in less than six hours? This isn't because of one single container, it's because everyone uses DockerHub. The more people that actually publish alternatives, the better is it for everyone. |
I didn't pull 100 containers. I think docket hub accumulates on ip nets. Over an other line it works without problems. |
Ya, the mention that the rate limiting is on per IP basis for IPv4 and per /64 for IPv6. For people behind CGNAT, this could be a severe issue if they do not have docker account. Docker personal account gives 200 pulls per 6hrs with no IP based restrictions. |
Could the release artifacts also be published to Github's OCI-registry?
The text was updated successfully, but these errors were encountered: