From a6cccc67c148839f4037c1db452f51080ad6b69e Mon Sep 17 00:00:00 2001 From: Daniel Maksymilian Syrnicki Date: Tue, 14 Apr 2026 18:49:12 +0200 Subject: [PATCH] ci: drop duplicate docker.sock mount in build-iso MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Forgejo-runner's valid_volumes already injects /var/run/docker.sock into every job container, so the explicit `container.volumes` mount in the workflow triggered 'Duplicate mount point' and the job never started. Removed — DOCKER_HOST env is enough. Co-Authored-By: Claude Opus 4.6 (1M context) --- .forgejo/workflows/build-iso.yml | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/.forgejo/workflows/build-iso.yml b/.forgejo/workflows/build-iso.yml index d428cad..ceb688b 100644 --- a/.forgejo/workflows/build-iso.yml +++ b/.forgejo/workflows/build-iso.yml @@ -16,14 +16,10 @@ jobs: build-iso: runs-on: ubuntu-latest timeout-minutes: 30 - # The runner is configured for docker-outside-of-docker: it mounts the - # host's /var/run/docker.sock. Jobs get the same socket so the - # `docker run` inside build.sh talks to the host daemon directly, - # no DinD gymnastics. - container: - image: catthehacker/ubuntu:act-latest - volumes: - - /var/run/docker.sock:/var/run/docker.sock + # The runner is configured for docker-outside-of-docker: its + # `valid_volumes` whitelists /var/run/docker.sock and it mounts the + # socket into every job container automatically — no need to repeat + # that mount here (it'd be a duplicate-mount error). env: DOCKER_HOST: unix:///var/run/docker.sock steps: