Docker Guide

Run SeleniumBase for Rust tests inside a container for reproducible CI/CD builds. This guide covers building the image, running the CLI, using Docker Compose, and configuring CI.

Build the image#

From the repository root:

docker build -t seleniumbase-rs .

Run the CLI#

The runtime image contains the compiled sbrs binary, Chromium and a matching chromedriver. The image’s entry point is sbrs, so the arguments after the image name are sbrs arguments. Run it headless:

docker run --rm seleniumbase-rs --helpdocker run --rm seleniumbase-rs doctordocker run --rm --shm-size=1g seleniumbase-rs --headless smoke 'data:text/html,<title>Smoke</title><h1>hi</h1>' --title-contains Smoke

sbrs open and smoke need --headless or SB_HEADLESS=true in a container (the flag beats the variable). The build, the test results on Linux arm64 and the commands that worked are in Building and Operating systems.

Docker Compose#

services:  tests:    build: .    environment:      - SB_HEADLESS=true    command: ["--help"]

docker compose up --build

CI/CD#

See .github/workflows/ for the GitHub Actions jobs:

Headless in Docker#

Always run browsers headless inside containers. sbrs and code that loads Settings read SB_HEADLESS=true; BrowserConfig::default() is already headless, and the pure CDP engine is headless on Linux unless told otherwise (see Headless and headed browsers).

The WebDriver engine always adds --no-sandbox on Linux. The pure CDP engine does not: if Chromium fails with a sandbox error there, set SB_NO_SANDBOX=1 (or LaunchOptionsBuilder::no_sandbox(true)).

let config = BrowserConfig::default().with_headless(true);

Troubleshooting#