Replies: 2 comments 2 replies
-
AIO could still go around this rate limit by applying to the Docker Verified Publisher Program: https://docs.docker.com/docker-hub/repos/manage/trusted-content/dvp-program / https://www.docker.com/partners/programs/ It includes: "Removal of rate limiting for developers", which means that there is no rate limit for all AIO docker images. Even if I personally think ghcr support would be a good idea, this would be no fix since there are, not sure, thousand of AIO instances running which will fail to update because of this limit |
Beta Was this translation helpful? Give feedback.
-
my thought, and I fully acknowledge it's easier said than done and more a long term not a tomorrow fix. because i fully expect this hub to be a issue everytime someone is deciding to try to cut costs, Is to inside the the AIO master webui. give an option to specify to pull from GHCR or HUB, this way it would give users a choice to choose an option, and could lay the ground work to at best get people to GHCR or as a compromise host the component images are at GHCR while the master aio image can be both GHCR and dockerhub (or where ever in the future), but just my random thoughts. there is of course some who deploy each part manually. but that's a slightly different matter. anywho. thanks for acknowledging. does seem like they decided to loosen up a bit and make a course adjust somewhat . with more pulls for authenticated.. |
Beta Was this translation helpful? Give feedback.
-
with the new dockerhub restrictions taking effect any plans to move aio to ghcr? someone not authenticated would easily blow through that 10 per hour limit with just aio
https://docs.docker.com/docker-hub/usage/
Beta Was this translation helpful? Give feedback.
All reactions