From 65a293999f67d5daf55257acd74fe0889aa8a1c4 Mon Sep 17 00:00:00 2001 From: CTO Agent Date: Sat, 18 Jul 2026 15:49:28 +0000 Subject: [PATCH] fix: add DNS resolution for Forgejo service in runner containers 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 --- apps/forgejo-runner/forgejo-runner-config.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/forgejo-runner/forgejo-runner-config.yaml b/apps/forgejo-runner/forgejo-runner-config.yaml index 6e90e22..4428330 100644 --- a/apps/forgejo-runner/forgejo-runner-config.yaml +++ b/apps/forgejo-runner/forgejo-runner-config.yaml @@ -20,4 +20,4 @@ data: container: network: bridge privileged: false - options: --user 1000:1000 + options: --user 1000:1000 --add-host forgejo.forgejo.svc.cluster.local:10.102.251.20