[🚀 Feature]: Support more container registries

[jjshoe]

Feature and motivation

Dockerhub has rate limits, and they are reasonable for grabbing just the selenium container. However you have to consider most modern environments where automation is king. This means many other containers are being pulled from dockerhub, many times a day, from all over inside an organization by CI/CD. The limit can quickly be hit by an extensive build job. It's not uncommon to hit rate limits, that don't exist on other registries, regularly with dockerhub.

Pushing to Github Container Registry, or Amazon pubilc ECR should be very trivial to do with the existing selenium pipeline. Unlike a previous closed issue on this repository said, no one has to update any of their code to switch registries. The suggestion is to add repositories, not replace.

Adding this flexibility also gives options in the case of outages with a particular registry.

CC: #1401

Usage example

Cases where this helps:

• Outages
• Rate limits
• Proximity to compute (aws)

[github-actions]

@jjshoe, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

The current GitHub plan is free, so we just worry about the storage limits for the long term. As storage usage could be seen in Docker Hub, it is up to Terabytes.

I think if a popular provider can sponsor us with an open-source plan for publishing images (unlimited storage), then we can push images and let users have more choices to use.

[jjshoe]

@VietND96 - https://docs.docker.com/docker-hub/repos/manage/trusted-content/official-images/ - If you work on becoming an official image in dockerhub, AWS automatically mirrors all of them https://aws.amazon.com/blogs/containers/docker-official-images-now-available-on-amazon-elastic-container-registry-public/

This seems like win win for everyone. I have not made an issue over in https://github.com/docker-library/official-images. It seems like that would be best made by someone from the selenium project. If you do make one, I would love to thumbs up it.

[VietND96]

Thanks for your info here. Let me try to work on upgrading "Official Images" to see how they respond.

[diemol]

I believe an official image for Docker is an image with a single purpose (or something like that). Our images have different purposes and components and that's why it was not possible to make them official. I've had meetings with folks from Docker and what he have so far is that Docker Selenium is a OSS sponsored project. IIRC, that means there are no quotas when pulling our images.

[diemol]

@jjshoe have you hit any rate limits? I think our images don't have them.

[jjshoe]

@jjshoe have you hit any rate limits? I think our images don't have them.

I have absolutely hit rate limits, rate limits is also only one of three bullet points.

[diemol]

Are you authenticating when pulling?