15 · Compute and housekeeping
Shared container host
One shared host: every run capped, labelled, cleaned hourly.
One rootless-podman host takes every work session's containers and image builds over a remote engine connection; each run is labelled and capped, and an hourly housekeeper stops what is overdue and prunes what is unused.
- 01One host, one rule — every run and image build goes to one shared host over a remote engine connection; the workstation runs no engine.
- 02Runs expire by label — two hours by default, twelve at most; a keep label exempts a shared image.
- 03Hourly housekeeping — a systemd timer stops overdue containers, prunes unused images and cache, and clears everything unused above 80% disk.
- 04Rehearse first — each installer has a read-only rehearsal, and the housekeeper a dry run.
- 05Capped CI runners — runners live on build hosts only, never on the production host, with their caps written down.
Internal
- 6 cleanup steps
- 2 h default run lifetime
- 80% disk trigger
SurfacesCLISelf-hosted
- Podman (rootless)
- Quadlet
- systemd timers
- GitLab Runner
- Bash
- Python