Fix Docker permission issues for admin user

- Add Docker socket permission check
- Implement fallback to sudo for docker commands
- Handle admin user Docker access limitations
- Add conditional logic for docker vs sudo docker-compose

Resolves: Docker socket permission denied errors

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.github/workflows/deploy.yml

@@ -51,9 +51,22 @@ jobs:
           tar czf - . | ssh -p ${{ secrets.NAS_PORT }} admin@${{ secrets.NAS_HOST }} \
             "cd /volume1/homes/admin/nginx-infra && tar xzf -"
 
+      - name: Check Docker permissions
+        run: |
+          ssh -p ${{ secrets.NAS_PORT }} admin@${{ secrets.NAS_HOST }} \
+            "ls -la /var/run/docker.sock && groups"
+
       - name: Remote docker-compose up
         run: |
-          ssh -p ${{ secrets.NAS_PORT }} ${{ secrets.NAS_USER }}@${{ secrets.NAS_HOST }} << 'EOF'
+          ssh -p ${{ secrets.NAS_PORT }} admin@${{ secrets.NAS_HOST }} << 'EOF'
             cd /volume1/homes/admin/nginx-infra
-            docker-compose up -d --build
+            
+            # Try with sudo if direct access fails
+            if ! docker ps > /dev/null 2>&1; then
+              echo "Using sudo for docker commands..."
+              sudo docker-compose up -d --build
+            else
+              echo "Direct docker access available..."
+              docker-compose up -d --build
+            fi
           EOF