No description
  • Dockerfile 100%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-09-29 23:45:15 +02:00
.forgejo/workflows ci: build on actions-base itself instead of catthehacker (bootstrap done) 2026-09-29 23:45:15 +02:00
Dockerfile actions-base: UBI 10 minimal with Node.js, git and the Docker CLI for Forgejo Actions 2026-09-29 23:42:38 +02:00
README.md actions-base: UBI 10 minimal with Node.js, git and the Docker CLI for Forgejo Actions 2026-09-29 23:42:38 +02:00

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.