From 64baf319fe2750b9ff957fe3e25d53e8438088b3 Mon Sep 17 00:00:00 2001
From: Julia McGhee <julia.eloise@pm.me>
Date: Sat, 21 Mar 2026 17:23:25 +0000
Subject: [PATCH] Fix runner: use explicit register + daemon with --config flag

The act_runner entrypoint ignores CONFIG_FILE for the daemon
command, so container.options (pnpm cache volume) never loads.
Use a custom command that registers manually then runs daemon
with --config explicitly.
---
 .../platform/gitea-runner/deployment.yaml        | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/infra/kubernetes/platform/gitea-runner/deployment.yaml b/infra/kubernetes/platform/gitea-runner/deployment.yaml
index 9633abc..286bcf3 100644
--- a/infra/kubernetes/platform/gitea-runner/deployment.yaml
+++ b/infra/kubernetes/platform/gitea-runner/deployment.yaml
@@ -18,9 +18,21 @@ spec:
       containers:
         - name: runner
           image: gitea/act_runner:latest
+          command:
+            - sh
+            - -c
+            - |
+              if [ ! -f /data/.runner ]; then
+                act_runner register \
+                  --instance "$GITEA_INSTANCE_URL" \
+                  --token "$GITEA_RUNNER_REGISTRATION_TOKEN" \
+                  --labels "$GITEA_RUNNER_LABELS" \
+                  --config /config/config.yaml \
+                  --no-interactive
+              fi
+              exec act_runner daemon --config /config/config.yaml
+          workingDir: /data
           env:
-            - name: CONFIG_FILE
-              value: /config/config.yaml
             - name: GITEA_INSTANCE_URL
               value: http://gitea-helm-http.platform.svc:3000
             - name: GITEA_RUNNER_REGISTRATION_TOKEN