From 3ca1a9af088a22da99276c5fcdaba52b2da347e7 Mon Sep 17 00:00:00 2001
From: Kyle Pope <kyle.a.pope@outlook.com>
Date: Wed, 18 Mar 2026 04:36:07 +0800
Subject: [PATCH] Fix act_runner: run as root for Docker socket access

group_add didn't resolve the permission issue. Running the runner
as root (user 0:0) is the standard approach for CI runners that
need Docker socket access on internal/single-user deployments.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 docker-compose.yaml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docker-compose.yaml b/docker-compose.yaml
index a6f2635..e61be19 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -66,8 +66,7 @@ services:
   act_runner:
     image: gitea/act_runner:latest
     restart: unless-stopped
-    group_add:
-      - "971"
+    user: "0:0"
     volumes:
       - act_runner_data:/data
       - /var/run/docker.sock:/var/run/docker.sock