Browsers
Every image is built on Ubuntu 26.04 LTS from a shared base layer, then a browser layer, then a driver layer.
| Browser | Version | Driver | Driver matches | |
|---|---|---|---|---|
 | Chrome | 152.0.7977.75 | ChromeDriver 152.0.7977.75 | exact build |
 | Firefox | 155.0.0 | geckodriver 0.37.1 | independent |
 | Edge | 152.0.4191.62 | Edge WebDriver 152.0.4191.62 | exact build |
 | Opera | 135.0.5973.76 | OperaDriver 151.0.7922.176 | Chromium line |
 | Brave | 1.94.119 (Chromium 152) | ChromeDriver 152.0.7977.75 | embedded Chromium |
 | Yandex | 26.6.1.1083 | yandexdriver | vendor fork |
 | Safari | WebKitGTK 2.52.6 | WebKitWebDriver | ships together |
The versions above are what the current images contain. Tags and the versioning policy are documented in Image tags.
How a browser is driven
Section titled “How a browser is driven”Every image runs a WebDriver server on port 4444 and the browser beside it. The differences are in how tightly the driver is coupled to the browser build:
- Chromium-family browsers (Chrome, Edge, Brave, Yandex, Opera) speak the same protocol through a chromedriver derivative. The driver enforces a version check against the browser, which is why each image pins a specific driver rather than tracking latest.
- Firefox uses geckodriver, versioned independently of Firefox and compatible across a wide range of releases.
- WebKit uses WebKitWebDriver, built from the same source tree as the engine, so the two always match.