christian/recurring-checklist
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Drop the duplicate docker.sock mount from the deploy job
Deploy web to NAS / deploy (push) Successful in 2m47s
Details

Browse Source 
act_runner already mounts /var/run/docker.sock into every job container, so
declaring it again in the workflow made the daemon refuse to create the
container at all: "Duplicate mount point: /var/run/docker.sock". The deploy
directory still has to be declared, and still at its own host path.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Waters Church
2026-09-24 14:02:51 -04:00
co-authored by Claude Opus 5
parent 00c2ad15a7
commit 1d40872127
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy.yml
+4 -1
View File
@@ -28,7 +28,10 @@ jobs:
container: container:
image: node:20-alpine image: node:20-alpine
volumes: volumes:
- /var/run/docker.sock:/var/run/docker.sock # The docker socket is deliberately NOT listed here: act_runner already mounts it
# into every job container, and declaring it again makes the daemon reject the
# container with "Duplicate mount point: /var/run/docker.sock".
#
# Mounted at the SAME path it has on the host. docker-compose.yml binds ./data # Mounted at the SAME path it has on the host. docker-compose.yml binds ./data
# relative to the compose file, and the daemon resolves that as a HOST path — so if # relative to the compose file, and the daemon resolves that as a HOST path — so if
# this were mounted anywhere else the app would come up pointed at a directory that # this were mounted anywhere else the app would come up pointed at a directory that