ColibriSec/forgejo-runner
Watch
1
0
Fork
You've already forked forgejo-runner
 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions
Forgejo Runner configuration repository
3 commits 1 branch 0 tags 7.7 KiB
  • Dockerfile 100%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
james-luther 50cf6a5874
All checks were successful
security-scan / scan (push) Successful in 34s
Details
build-and-push / build (push) Successful in 1m31s
Details
Add jq: also missing from the base image, needed by ojo-forgejo's PR-comment feature
2026-09-04 21:24:59 -05:00
.forgejo/workflows Add jq: also missing from the base image, needed by ojo-forgejo's PR-comment feature 2026-09-04 21:24:59 -05:00
.gitignore Add runner image: node:22-bookworm + docker CLI 2026-09-04 15:43:46 -05:00
Dockerfile Add jq: also missing from the base image, needed by ojo-forgejo's PR-comment feature 2026-09-04 21:24:59 -05:00
README.md Add runner image: node:22-bookworm + docker CLI 2026-09-04 15:43:46 -05:00

README.md

forgejo-runner

Runner image for git.colibrisec.org's act_runner. This instance's ubuntu-latest label maps to a plain node:22-bookworm container with no docker CLI, so every workflow that shells out to docker run had to install it itself. This image just adds that on top of the same base, so it's a drop-in replacement.

Usage

Build and push happen automatically on any push to main that touches Dockerfile (or via the workflow_dispatch button). To actually put it to use, point act_runner's config.yaml label mapping at forgejo-http.forgejo.svc.cluster.local:3000/colibrisec/forgejo-runner:latest instead of node:22-bookworm, then restart the runner. That part isn't something a workflow in this repo can do -- it's runner-host config, done by hand.

Once that's live, drop the "Install docker CLI" step from any workflow that only needed it because of the old base image (balam's build.yml and security-scan.yml, at least).