Skip to content

docker-lab.md

Latest commit

 

History

History
49 lines (40 loc) · 2.17 KB

docker-lab.md

File metadata and controls

49 lines (40 loc) · 2.17 KB
Raw

Docker lab

scripts/docker-lab runs a command in a Linux container that has Rust and Playwright's Chromium with its system libraries (docker/lab/Dockerfile). Use it for anything that launches a browser, or that writes and runs throwaway browser scripts. That includes the agent-browser test suite, whose fixtures write fake chrome shell scripts to temporary directories and execute them. Running those on a Mac can trip macOS malware protection. Inside the container they touch nothing on the host except the mounted source tree.

Usage

# a shell in this repository
scripts/docker-lab

# this repository's contract commands on Linux
scripts/docker-lab -- cargo test --all-features

# the browser stack against the travel fixture (no Jev), then a full task
scripts/docker-lab -- crates/tinycomputer-examples/fixtures/run browser_fixture
scripts/docker-lab -- crates/tinycomputer-examples/fixtures/run task_fixture

# another checkout, e.g. agent-browser's crate
scripts/docker-lab --src ../agent-browser --workdir cli -- cargo test --profile ci
Option Meaning
--src DIR directory mounted read-write at /src (default: this repository)
--workdir SUBDIR where under /src the command runs
--rebuild rebuild the image even if it exists

Operational notes

  • The image tag is derived from the Dockerfile's hash, so editing the Dockerfile builds a fresh image on the next run.
  • Build output goes to <workdir>/target/docker-lab, beside the host's target/. Linux and macOS artifacts never share a directory, and tune-box --clean-targets still finds it.
  • The cargo registry is cached in the tinycomputer-lab-cargo volume. Remove it with docker volume rm tinycomputer-lab-cargo.
  • PLAYWRIGHT_BROWSERS_PATH=/ms-playwright is set. agent-browser searches that path for Chromium, and adds --no-sandbox itself inside a container.
  • .env is loaded the way scripts/lab loads it, and only OPENROUTER_API_KEY and TINYCOMPUTER_LAB_MODEL are forwarded into the container, by name. Nothing is printed.
  • The container has no display. Headed browser runs, and anything that drives macOS applications, still need the host (scripts/lab).