Linux
The image also carries the libraries Playwright’s Chromium loads, and
Liberation Sans, which fontconfig gives Chromium for Arial. It does not carry
Chromium itself: a job downloads the browser its lockfile names.
A Linux job runs as UID/GID 1000 with
HOME set to /home/runner. Its root is
read-only and the runner runs with no_new_privs, so a job has no sudo and no
apt. Its writes go to a 30 GiB encrypted scratch disk: checkouts, build
outputs, the tool cache, RUNNER_TEMP, home caches (npm, pip, cargo, …),
/tmp and /var/tmp.
macOS
Homebrew comes first on the job’s
PATH, before the system’s directories;
cmake and zstd come after them. The zstd and metal-cpp files are there
because jobs and their actions call them without installing them:
actions/cache compresses with zstd when zstd --quiet --version answers, and
MLX’s CMake build can use the pinned metal-cpp archive instead of downloading
it.
A macOS job has a Metal GPU: the VM’s paravirtualized device. MLX, MPS and
simdgroup matrices run at the host GPU’s speed, but the device reports its
architecture as air64_v27, never the host’s applegpu_* name. A check that
compares the architecture a library picks with the host’s name fails in every
macOS VM, Blacksmith’s included.
Add tools a job needs
- Linux: install into the scratch disk (the checkout,
HOME,RUNNER_TEMPor a tool cache) or use an action such asactions/setup-*that does. There is noaptand nosudo. A tool the image should provide for every job is an image change: ask your Darkbloom contact. - macOS:
brew installworks for the job, and Homebrew comes first onPATH. A tool you install exists only for that job’s VM. - Both: a tool you download needs a host Darkbloom approved for your repository (caching and network). Pin the version you download; an image update can change a tool’s version.
- Caches:
actions/cacheand the tools built on it work unchanged. See caching and network for where a cache is stored and when a job misses it.

