From ccb910856341d597e133ce02116df2c8798ece9f Mon Sep 17 00:00:00 2001 From: Michal Date: Mon, 9 Mar 2026 00:27:59 +0000 Subject: [PATCH] ci: restart dockerd directly (no service manager in runner) The Gitea Act Runner container has no systemd, service, or init.d. Kill dockerd by PID and relaunch it directly after writing daemon.json. Co-Authored-By: Claude Opus 4.6 --- .gitea/workflows/ci.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index 651979a..88303f7 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -148,12 +148,12 @@ jobs: run: | sudo mkdir -p /etc/docker echo '{"insecure-registries":["${{ env.GITEA_REGISTRY }}"]}' | sudo tee /etc/docker/daemon.json - # Restart docker - try systemctl first, fall back to service for non-systemd runners - if command -v systemctl &>/dev/null && systemctl is-system-running &>/dev/null; then - sudo systemctl restart docker - else - sudo service docker restart || sudo /etc/init.d/docker restart - fi + # Restart dockerd - kill existing process and relaunch + sudo kill "$(cat /var/run/docker.pid 2>/dev/null)" 2>/dev/null || sudo pkill dockerd || true + sleep 3 + sudo dockerd &>/dev/null & + # Wait for Docker to be ready + for i in $(seq 1 30); do docker info &>/dev/null && break || sleep 1; done - name: Login to Gitea container registry run: |