[🚀 Feature]: Push containers to both Docker Hub and GHCR

[erseco]

Feature and motivation

Referencing #1401 and considering the new Docker Hub rate limit restrictions, it might be a good idea to publish the images to both Docker Hub and GHCR.

• GHCR provides faster pulls with no rate limits.
• Existing users can continue using Docker Hub without changes.
• Users who prefer GHCR only need to prefix with ghcr.io/seleniumhq/....

This dual publishing strategy would give the community more flexibility and resilience against Docker Hub limitations.

Usage example

Users who prefer GHCR could simply pull images like this:

docker pull ghcr.io/selenium/standalone-chrome:latest
docker run -d -p 4444:4444 ghcr.io/seleniumhq/standalone-chrome:latest

This avoids Docker Hub rate limits while keeping compatibility for those still pulling from Docker Hub.

[github-actions]

@erseco, 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]

Can you read this? #2798 (comment)
Just register a free account on Docker Hub and docker login, you can pull without limit rate. Can you verify this?

[erseco]

Thank you very much for the clarification regarding Docker Hub rate limits. This partially solves my needs.

That said, there are still some scenarios where having the images also available on GHCR would be useful — for example, users running tests locally without having a Docker Hub account, or in GitHub Actions pipelines when working from forks. It would also provide resilience in case Docker Hub has an outage.

If you think this is out of scope for now, feel free to close the issue. Thanks again for your time and support. 🙏

[KyleAure]

I think many other developers would also appreciate these images being available in alternative registries.
In the past 5 years DockerHub has become more and more restrictive when it comes to things like rate limits and usage licensing. I would appreciate it if these images were available from an alternative source such as ghcr.io.

[erseco]

Since this issue did not get much traction, last year I decided to build and maintain my own lightweight container for E2E testing based on Alpine Linux, including ChromeDriver.

I publish the images to both Docker Hub and GHCR, mainly because having more than one registry gives users more flexibility and avoids depending on a single provider.

Repository:
https://github.com/erseco/alpine-chromedriver

From my experience, dual publishing is practical for local development, CI pipelines, and situations where Docker Hub limits or availability become a problem.

[amyreit]

My company no longer allows us to pull images from DockerHub - we would really appreciate having them in ghcr.io instead of having to add building our own into our pipeline. I'd love a standalone-firefox image (hint hint)

[cgoldberg]

@VietND96 is this something you could do? It sounds like it would be useful to have official images in an alternate container registry.

[VietND96]

@cgoldberg I can do the deployment, hopefully GH Container registry allows enough space for our images push, since I also shared the current storage on Docker Hub as of now #2798 (comment)

[KyleAure]

It looks like a similar question about storage limits in ghcr.io was raised here: https://github.com/orgs/community/discussions/183054

Perhaps until we have a clear answer from GitHub on how they plan to handle widely used OSS community images we could start with just dual publishing a subset of images to ghcr.io. Maybe just standalone-chrome and standalone-firefox. And only dual publish point releases and skip dual publishing dev/nightly builds.

Doing a soft launch like this would also give us data on pull rates to see how many people switch over.

Unfortunately the reality is any of these companies (docker, github, aws, ect.) have the power to pull the rug out from us at any time even though we provide so much of the value these platforms. :(

[VietND96]

Image tags nightly are now available for all images. The next deployment onwards (including latest) will also be available soon.

[cgoldberg]

@VietND96 nice work! Thanks for getting this done