vemonet commented on issue #3165: URL: https://github.com/apache/jena/issues/3165#issuecomment-2850599179
Thanks @rvesse , I did not know about these limitations for ghcr. My guess is that every single public container registry will have some kind of limitations to prevent abuse of their system Known limitations: - GitHub Container Registry: 700 request per minute ([global apparently](https://github.com/aquasecurity/trivy-action/issues/389)) - DockerHub: 100 every 6h per IP address (https://docs.docker.com/docker-hub/usage/) Our experience with DockerHub is that you can easily reach their limit when deploying on a shared kubernetes cluster, requiring you to do additional work either to switch the IP address or login to DockerHub to raise the limitations But Dockerhub has an open source program you can apply to that will lift rate limits: https://www.docker.com/community/open-source/application/ > No reason not to publish to multiple registries including DockerHub, though the project would likely need to talk to Infra to figure out the AuthN for that. > GHCR is probably easier option in short term Agree with that. More can be better, but simplicity and reliability also has value when maintaining systems on the long run I am not knowledgeable on Apache policies, but from a quick search it seems like there are no requirements on which registry should be used. The most commonly used is `apache/` org on DockerHub (e.g. flink, kafka, probably because it was the first public registry), but some projects are using ghcr.io (e.g. yetus) On our side for now we just want to have 1 image, ideally available through a container registry that does not requires login -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
