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 <noreply@paperclip.ing>
This commit is contained in:
parent
0c66aa5eb6
commit
65a293999f
1 changed files with 1 additions and 1 deletions
|
|
@ -20,4 +20,4 @@ data:
|
||||||
container:
|
container:
|
||||||
network: bridge
|
network: bridge
|
||||||
privileged: false
|
privileged: false
|
||||||
options: --user 1000:1000
|
options: --user 1000:1000 --add-host forgejo.forgejo.svc.cluster.local:10.102.251.20
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue