eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Rename containers/forgejo-runner to runner-job-image
All checks were successful
Build Container (Nix) / detect (push) Successful in 2s
Details
Build Container / detect (push) Successful in 2s
Details
Build Container (Nix) / build (runner-job-image) (push) Successful in 2s
Details
Build Container / build (runner-job-image) (push) Successful in 1m42s
Details

Browse source 
The forgejo-runner container is the CI job execution environment (Dagger,
ArgoCD CLI, etc.), not the runner daemon itself. Rename to runner-job-image
to fix the version-check false positive (Dagger 0.19.11 vs daemon 12.7.0)
and clarify the distinction.

RUNNER_LABELS still references the old image name — will update after
building the image under the new name.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-02-23 17:44:51 -08:00
commit 4c5e0f0d16
4 changed files with 14 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/how-to/configuration/update-documentation.md
View file

@ -67,7 +67,7 @@ Fragments are automatically collected into `CHANGELOG.md` (at repo root) during
The workflow runs on the `k8s` label, which uses the [[forgejo]]-runner in Kubernetes:
- **Runner deployment**: `argocd/manifests/forgejo-runner/`
- **Job image**: `registry.ops.eblu.me/blumeops/forgejo-runner:latest`
- **Job image**: `registry.ops.eblu.me/blumeops/runner-job-image` (commit-SHA tagged)
- **Build engine**: [[dagger]] CLI installed at runtime; Node.js and Python run inside Dagger containers
The job image is built from `containers/forgejo-runner/Dockerfile`.