ci: restart dockerd directly (no service manager in runner)
Some checks failed
CI/CD / typecheck (push) Successful in 41s
CI/CD / test (push) Successful in 52s
CI/CD / lint (push) Successful in 10m47s
CI/CD / build (push) Failing after 7m31s
CI/CD / docker (push) Has been skipped
CI/CD / publish-rpm (push) Has been skipped
CI/CD / deploy (push) Has been skipped

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 <noreply@anthropic.com>
This commit is contained in:
Michal
2026-03-09 00:27:59 +00:00
parent d7b5d1e3c2
commit ccb9108563

View File

@@ -148,12 +148,12 @@ jobs:
run: | run: |
sudo mkdir -p /etc/docker sudo mkdir -p /etc/docker
echo '{"insecure-registries":["${{ env.GITEA_REGISTRY }}"]}' | sudo tee /etc/docker/daemon.json 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 # Restart dockerd - kill existing process and relaunch
if command -v systemctl &>/dev/null && systemctl is-system-running &>/dev/null; then sudo kill "$(cat /var/run/docker.pid 2>/dev/null)" 2>/dev/null || sudo pkill dockerd || true
sudo systemctl restart docker sleep 3
else sudo dockerd &>/dev/null &
sudo service docker restart || sudo /etc/init.d/docker restart # Wait for Docker to be ready
fi for i in $(seq 1 30); do docker info &>/dev/null && break || sleep 1; done
- name: Login to Gitea container registry - name: Login to Gitea container registry
run: | run: |