Skip to content

ci-base

Minimal Wolfi CI base image — bash, git, curl, jq, python3. The shared base every phpboyscout toolchain image derives from.

Release v0.3.5, 2026-11-19. Built on nothing in this group. Source: phpboyscout/images/ci-base.

Pin it

image: registry.gitlab.com/phpboyscout/images/ci-base:v0.3.5

Pin the full version. Each release also moves its minor tag and latest, which change under you.

Variant Tags
default v0.3.5, v0.3

About this image

The minimal Wolfi base image every phpboyscout toolchain image derives from, and the runtime for the CI jobs that need no toolchain at all.

registry.gitlab.com/phpboyscout/images/ci-base:vX.Y.Z

Contains bash, git, curl, jq, python3, sigillum and their certificates. Nothing else.

Why it exists

The consolidated images were being pulled for work that needed almost none of them. discord-release pulled 2.36 GB to run curl and jq; release-stamp, release-train and renovate-merge each pulled 2.72 GB to run a standard-library-only Python script.

Size CVEs
infra-tools ~2.36 GB 665
dev-tools ~2.72 GB 2,582
ci-base 48 MB 0

Why Wolfi

Measured on the same package set, the Debian system layer carries 2,468 findings (20 CRITICAL, 235 HIGH); the Wolfi one carries zero.

Wolfi is glibc-based, which is load-bearing rather than incidental: every prebuilt binary the toolchain images fetch — cargo-binstall running --disable-strategies compile, goreleaser-pro, syft, the AWS CLI v2 installer — is built against glibc and has no musl fallback. An Alpine base would break all of them.

Why the base is pinned by digest

cgr.dev/chainguard/wolfi-base publishes exactly one real tag, latest — the rest of its tag list is cosign .sig / .att / .sbom artefacts. There is no version to pin to, so a bare :latest would be a floating base. The digest is pinned and Renovate's dockerfile manager keeps it moving.

Non-root by default

Runs as ci (uid 1000), matching the posture of the components moving onto it. A base that quietly promoted them to root would be a privilege increase shipped as a size optimisation. Derived images needing root say so explicitly.

Deriving from it

FROM registry.gitlab.com/phpboyscout/images/ci-base:vX.Y.Z
USER root
RUN apk add --no-cache <your tools>

Package names are not one-to-one with Debian's: build-base for build-essential, pkgconf for pkg-config, openssl-dev for libssl-dev, dbus-dev for libdbus-1-dev.

SHELL ["/bin/bash", ...] must come after an apk add bash. Wolfi's base ships busybox ash; setting it earlier makes the next instruction fail with an exec error.

How sigillum is verified

sigillum comes from the release store at pkg.phpboyscout.uk, which is mutable, so a tarball checked only against a checksums file from the same store proves nothing. The build checks the store's OpenPGP signature over checksums.txt first, with gpgv, in a throwaway stage. Neither gpgv nor the key reaches the image.

The key is committed in keys/, and its primary fingerprint is pinned in the SIGILLUM_KEY build argument. The build fails unless the signature is valid and made by that fingerprint.

To add or rotate the key, take it from https://keys.phpboyscout.uk/, confirm its fingerprint against the one go-tool-base pins in cli/pkg/trustkeys/trustkeys_test.go on main, and move the key file and SIGILLUM_KEY in one commit. A revoked key keeps verifying until that commit lands: gpgv sees no revocation.

Releases

Trunk-based, driven by colophon. A merge to main opens or updates a Release MR, and merging that cuts the vX.Y.Z tag whose pipeline publishes the image.

The scan comes from the cicd image-scan component. scan:os gates: a fixable HIGH or CRITICAL finding in the system packages fails the pipeline. scan:tools reports on the one bundled binary, sigillum, and is advisory, as it is on every image that leaves the component's default.

Design record

cicd spec 0074

Everything installed

Contents not yet published. This image's releases do not carry an SBOM yet. Until they do, the README above describes what it adds, and the Dockerfile is the full record.