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

Migrate Forgejo runner to Kubernetes with DinD #60

Merged
eblume merged 15 commits from feature/containerized-runner into main 2026-01-25 19:56:17 -08:00
Conversation 0 Commits 15 Files changed 14 +3 -3
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit c4b14c0b89 - Show all commits

Move DOCKER_HOST to runner config instead of workflow
Some checks failed
Build Container / build (push) Failing after 59s
Details

Prev Next 
The runner's container.env config sets environment variables in all
job containers, so we don't need to specify DOCKER_HOST per-workflow.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Erich Blume 2026-01-25 19:40:33 -08:00
commit c4b14c0b89

3
.forgejo/workflows/build-container.yaml
View file

@ -16,9 +16,6 @@ on:
jobs: jobs:
build: build:
runs-on: k8s runs-on: k8s
env:
# For k8s runner with DinD sidecar, Docker is available via TCP
DOCKER_HOST: tcp://127.0.0.1:2375
steps: steps:
- name: Parse tag - name: Parse tag
id: parse id: parse

3
argocd/manifests/forgejo-runner/configmap.yaml
View file

@ -18,3 +18,6 @@ data:
network: "host" network: "host"
# Connect to DinD sidecar via TCP (not socket) # Connect to DinD sidecar via TCP (not socket)
docker_host: tcp://127.0.0.1:2375 docker_host: tcp://127.0.0.1:2375
# Set DOCKER_HOST in job containers so they can run docker commands
env:
DOCKER_HOST: tcp://127.0.0.1:2375