- Dockerfile 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Extends the matrix: alma{9,10}-tester (dnf) + ubuntu{2204,2404}-tester (apt),
each built per-arch (:v1-{amd64,arm64}). Same minimal pattern — stock distro +
baked mc; file:// gate needs no ca-certs.
|
||
| images | ||
| README.md | ||
tester-images
Generic, single-purpose "install a package from a repo, then run it to prove it
works" container images — one per (distro, arch). NOT specific to any one
project: each image is a stock distro with only the MinIO client mc baked in, so
any pipeline can mc cp a staged apt/dnf repo, install the package natively, and
smoke-run it.
Kept separate from builder-images (which holds images that build things) — these
test things.
Layout
images/<distro><ver>-tester/Dockerfile — e.g. images/debian13-tester/.
Multi-arch
Each tester is built per-arch and published as :v1-amd64 / :v1-arm64, then
crane-merged into the auto-selecting manifest list :v1 (the cluster
multiarch-image-build-standard). The arm64 variant runs on the amd64 cluster via
qemu-user binfmt — a package install + a --version smoke is light enough for
emulation.
Current images
| Image | Base | Use |
|---|---|---|
debian13-tester |
debian:13 (trixie) |
apt install + run, current stable |
debian12-tester |
debian:12 (bookworm) |
apt install + run, n-1 stable |
Alma (alma9-tester, alma10-tester) and Ubuntu testers follow the identical
pattern when added.
Canonical / mirror
Forgejo (code.sean.farm/seanfarm/tester-images) is canonical in-cluster; an
XGitMirror seeds it from codeberg.org/someara/tester-images on cluster build
and push-mirrors it back every 10 min. Push day-to-day to Forgejo.