seleniumhq/docker-selenium

Provides a simple way to run Selenium Grid with Chrome, Firefox, and Edge using Container Platform, making it easier to perform browser automation at scale

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 7th, 2026
Created on November 17th, 2014
Open Issues & Pull Requests: 87 (+0)
GitHub issues: Enabled
Number of forks: 2,548
Total Stargazers: 8,652 (+0)
Total Subscribers: 241 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.5 hours
Mean response time: 7.9 days
90th percentile: 6.4 days
Tracked items: 248

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "R-awaiting-answer" is answered fastest, typically in about 3 hours, while "enhancement" waits about 30 hours. Only 5% of issues opened in the past year have been closed. Three people close 75% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 74
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 517 days
Stale 30+ days: 62
Stale 90+ days: 60

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 4

Top labels

  • needs-triaging (150)
  • R-awaiting-answer (58)
  • enhancement (14)
  • I-autoscaling-k8s (10)
  • I-defect (7)
  • R-awaiting-merge (5)
  • R-awaiting-external-changes (4)
  • R-awaiting-retest (4)

Detailed Description

Docker Selenium is a containerized distribution of Selenium Grid that packages Chrome, Firefox, and Edge browsers for browser automation at scale.

The project solves the operational complexity of deploying and managing Selenium Grid infrastructure by providing pre-built Docker images that encapsulate the Grid hub and node components along with browser drivers. Rather than assembling these pieces manually, users pull ready-to-use images from a registry and orchestrate them through their container platform. The approach abstracts away configuration details and dependency management, allowing teams to focus on test execution rather than infrastructure setup.

Teams running browser automation tests in containerized environments should adopt this tool. It suits projects that need distributed test execution across multiple browser instances, particularly those already using Docker or Kubernetes. The project provides standalone images for simpler single-machine setups and hub-node configurations for scaled deployments. A Helm chart is available for Kubernetes users who want declarative Grid deployment. The tool is maintained as part of the official Selenium project, ensuring alignment with Selenium Grid releases and WebDriver standards.

The project receives regular maintenance with ongoing commits and releases. Docker images are published to a public registry with multiple tagged variants to support different deployment patterns. The codebase is written primarily in Go. Documentation includes setup guidance and community support channels are available through the Selenium project's support infrastructure.