feat: custom forgejo-runner-node image with docker.io pre-installed
Build forgejo-runner-node image / build (push) Failing after 30s

- Dockerfile.node extends node:22-bookworm + docker.io
- CI workflow builds and pushes to forgejo registry on changes
- values-node.yaml references custom image instead of stock node
- Removes need to install docker in every workflow using node runner
This commit is contained in:
2026-09-05 14:20:42 -07:00
parent ba4261fb39
commit acc11d5e87
3 changed files with 62 additions and 3 deletions
+4 -3
View File
@@ -2,11 +2,12 @@
# runner instance. Only runner.name and runner.labels differ -- everything
# else (image, dind, persistence, tolerations, nodeSelector) is shared.
#
# node:22-bookworm ships Node natively, so unlike the golang/rust instances,
# jobs on this runner need no "install node" step before actions/checkout.
# forgejo-runner-node extends node:22-bookworm with docker.io, so Node + Docker
# are both available. Built and pushed via homelab CI (build-runner-node.yml).
runner:
name: node-runner
labels: "node:docker://node:22-bookworm"
# Custom image extends node:22-bookworm with docker.io pre-installed
labels: "node:docker://forgejo.riotpiao.com/rock/forgejo-runner-node:latest"
# GC CronJob renders only from the default (golang) values to avoid duplicates
gc: