Pinned container images for ComlineProject's CI. Workflows run their jobs in an
image from here (container:) instead of installing tools on a floating
ubuntu-latest runner at run time, so a mirror outage or a new tool release
cannot break a job that did not change.
One image per kind of job, each carrying only what those jobs use:
| Image | For | Has |
|---|---|---|
ghcr.io/comlineproject/ci-bench |
the instruction-count benchmarks | Rust stable, valgrind, iai-callgrind-runner, python3, gh |
ghcr.io/comlineproject/ci-fuzz |
the cargo-fuzz jobs | Rust nightly, cargo-fuzz, gh |
ghcr.io/comlineproject/ci-wasm |
the WebAssembly build | Rust stable with wasm32, wasm-bindgen, wasm-pack, binaryen |
ghcr.io/comlineproject/ci-tools |
cue, cbindgen and the musl build | Rust stable with musl, cue, cbindgen, musl-tools, make, jq |
ghcr.io/comlineproject/ci-flatpak |
the sandbox tests of the VSCodium extension | Flatpak, bubblewrap, xdg-dbus-proxy, a session bus, Flathub's VSCodium and its runtime (amd64 only) |
All are Debian 13 (trixie) slim, by digest, with every apt package pinned to
one snapshot.debian.org date, for linux/amd64 and linux/arm64 (ci-flatpak:
linux/amd64 only, as Flathub's VSCodium is built for x86_64 here). The four
Rust images have git and a C toolchain; ci-flatpak has git and no compiler. images/versions.md lists
every version and why it is that one; docs/base-choice.md
says why Debian.
Pin the image by digest, never by tag. The digest of each build is in its
workflow run's summary. The builds are
reproducible (images/versions.md): a
digest changes only when an input of the image does.
jobs:
test:
runs-on: ubuntu-24.04
container:
image: ghcr.io/comlineproject/ci-tools@sha256:<digest>
steps:
- uses: actions/checkout@...
- run: cargo buildThe bench job's container needs --security-opt seccomp=unconfined:
iai-callgrind's runner switches ASLR off with setarch -R, which Docker's
default seccomp profile refuses.
container:
image: ghcr.io/comlineproject/ci-bench@sha256:<digest>
options: --security-opt seccomp=unconfinedThe flatpak job's container needs --privileged: bubblewrap makes namespaces
and mounts /proc, which Docker's default seccomp profile and masked paths
refuse. It runs as root, as every job container does, with XDG_RUNTIME_DIR
(/run/user/0) set; the job's dbus-run-session -- flatpak run ... is its own
session bus. VSCodium is installed for the whole system at an exact Flathub
commit, which /etc/ci-flatpak/vscodium-commit (and the image's
org.comlineproject.ci-flatpak.vscodium-commit label) holds, so a job can log it.
container:
image: ghcr.io/comlineproject/ci-flatpak@sha256:<digest>
options: --privilegedRenovate bumps the digest: the tags (latest, sha-<short>) exist for it to
follow. A bump is a pull request in the consuming repository, so it runs that
repository's CI against the new image before it merges.
Notes for jobs in the container:
stable(ornightly, inci-fuzz) names the pinned toolchain, so arust-toolchain.tomlwithchannel = "stable"andcargo +nightly fuzzneed no download.$CI_RUST_STABLEor$CI_RUST_NIGHTLYholds its exact name. Do not runrustup update.- The toolchains are minimal: no
clippy,rustfmtorllvm-tools-preview. A toolchain or component not in the image (beta, miri, a version arust-toolchain.tomlpins that the image does not have) is installed by the job.CARGO_HOMEandRUSTUP_HOME(/usr/local/cargo,/usr/local/rustup) are writable by any uid. - Node is not in the images; use
actions/setup-node.
Each published digest has a build provenance attestation:
gh attestation verify oci://ghcr.io/comlineproject/ci-bench@sha256:<digest> --owner ComlineProjectimages/Dockerfile is one file with a base stage and a
build target per image (docker build --target bench images).
build.yml builds the five images for both
architectures natively (ubuntu-24.04 and ubuntu-24.04-arm; ci-flatpak
only on the first). Every build
smoke-tests the image (images/smoke.sh, one mode per image:
each tool's version, a build for each target, with no network, as root and as
another uid), prints its compressed size, ci-bench runs core's bench at a
fixed commit, and ci-flatpak runs VSCodium's Electron inside Flatpak's
sandbox in a --privileged container (images/flatpak-sandbox-check.sh). Pull requests stop there. Pushes to main and manual runs on
main push each architecture by digest, smoke-test what was pushed, join the
two into one manifest tagged sha-<short> and latest, attest it, and run
core's bench in the published ci-bench and the sandbox check in the published
ci-flatpak as real container: jobs.
There is no scheduled rebuild: the apt packages are fixed by date, so a rebuild
would change nothing. To update them, move DEBIAN_SNAPSHOT (and the base
digest) in the Dockerfile. To update a tool, change the ARG and its hashes in
images/Dockerfile, and its row in
images/versions.md. ci-flatpak's VSCodium and runtime
are bumped the same way, by commit (images/versions.md
says how to find them).