65a293999f
Add --add-host mapping for forgejo.forgejo.svc.cluster.local to the Forgejo service ClusterIP (10.102.251.20) in the runner container options. This fixes the DNS resolution issue where workflow containers created by the runner (via Docker-in-Docker) cannot resolve Kubernetes service DNS names, causing the actions/checkout step to fail with "Could not resolve host: forgejo.forgejo.svc.cluster.local". Co-Authored-By: Paperclip <noreply@paperclip.ing>
23 lines
538 B
YAML
23 lines
538 B
YAML
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: forgejo-runner-config
|
|
namespace: forgejo
|
|
data:
|
|
config.yaml: |
|
|
log:
|
|
level: info
|
|
runner:
|
|
name: k3s-runner-1
|
|
capacity: 2
|
|
labels:
|
|
- "ubuntu-latest:docker://node:24-bookworm"
|
|
- "ubuntu-22.04:docker://node:24-bookworm"
|
|
timeout: 3h
|
|
cache:
|
|
enabled: true
|
|
dir: /data/cache
|
|
container:
|
|
network: bridge
|
|
privileged: false
|
|
options: --user 1000:1000 --add-host forgejo.forgejo.svc.cluster.local:10.102.251.20
|