Drop the duplicate docker.sock mount from the deploy job

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>

.gitea/workflows/deploy.yml

@@ -28,7 +28,10 @@ jobs:
     container:
       image: node:20-alpine
       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
         # 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