- Dockerfile 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| .forgejo/workflows | ||
| Dockerfile | ||
| README.md | ||
actions-base
Base image for Forgejo Actions jobs on the homelab runner (runner01): Red Hat UBI 10 minimal
with Node.js (for JavaScript actions such as actions/checkout), git, jq, tar and the Docker
CLI with buildx. Jobs get the runner's Docker socket, so they can build, run and push images.
forgejo.dmeg.se/nollverket/actions-base:latest
The runner's docker label points at :latest with force_pull: true (server-automation,
roles/forgejo_runner), so every runs-on: docker job without its own container: uses it.
Build
.forgejo/workflows/ci.yml builds and smoke-tests the image on every pull request and push, and
pushes :latest, :10 and :sha-<commit> from main, from manual runs and from a weekly
rebuild (Mondays 03:17) that picks up UBI and Node.js security updates.
Pinned in the Dockerfile: the Docker CLI (static build from download.docker.com) and buildx
(checksum-verified). Bump them there.
Rollback: if a rebuild breaks jobs, point the runner label at a previous :sha-<commit> tag.
Bootstrap: the first build ran on ghcr.io/catthehacker/ubuntu:act-22.04, since this image
didn't exist yet. Since then the workflow builds the image on itself.