From f22e93963e65bfa10d9e50d1f9da13a8ef0da4ed Mon Sep 17 00:00:00 2001 From: Lucas Seidelin Rosenvold Christensen Date: Fri, 18 Sep 2026 15:25:18 +0200 Subject: [PATCH] Drop custom dind sidecar, use runner-provided docker daemon The Forgejo runner infra now gives job containers a privileged container pre-wired to its own dind sidecar via DOCKER_HOST, so defining our own docker:dind service would start a conflicting second daemon. Keep the node image + docker CLI install (still needed) and drop the services/env block. Co-Authored-By: Claude Sonnet 5 --- .forgejo/workflows/build.yml | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/.forgejo/workflows/build.yml b/.forgejo/workflows/build.yml index 7a7eddd..c1e4846 100644 --- a/.forgejo/workflows/build.yml +++ b/.forgejo/workflows/build.yml @@ -9,16 +9,10 @@ jobs: build-and-push: runs-on: docker # actions/checkout & co. are JS actions and need Node, so the job - # container has to be a Node image (not a bare docker CLI image). We - # install the Docker CLI into it and talk to a sidecar dind daemon over - # the network instead of relying on the runner exposing a host socket. + # container has to be a Node image (not a bare docker CLI image). The + # runner already provides a privileged container wired up to its own + # dind sidecar via DOCKER_HOST, so we just need the docker CLI itself. container: node:20-bookworm - services: - docker: - image: docker:27-dind - options: --privileged - env: - DOCKER_HOST: tcp://docker:2375 steps: - name: Checkout uses: actions/checkout@v4