From 431e2c0a5fe69d75eca904906b9e3c00a3641a45 Mon Sep 17 00:00:00 2001 From: "Gan, Jimmy" Date: Sat, 4 Apr 2026 02:13:10 +0800 Subject: [PATCH] fix: execute docker commands on NAS host via SSH The Docker-in-Docker limitation prevents creating containers with external networks from within the workflow container. Execute the deploy commands directly on the NAS host via SSH to avoid this issue. This is similar to how manual execution works - running docker compose directly on the host where all networks are accessible. --- .gitea/workflows/deploy-dev.yml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/.gitea/workflows/deploy-dev.yml b/.gitea/workflows/deploy-dev.yml index 362b679..69b8dc3 100644 --- a/.gitea/workflows/deploy-dev.yml +++ b/.gitea/workflows/deploy-dev.yml @@ -64,7 +64,6 @@ jobs: - name: Deploy dev run: | export DOCKER_API_VERSION=1.43 - cd /nas-dashboard - # Remove old container completely, then create fresh - docker rm -f nas-dashboard-dev || true - docker compose -f docker-compose.dev.yml up -d --pull never + # Execute deploy script on NAS host directly (not from workflow container) + # This avoids Docker-in-Docker network connection issues + ssh -o StrictHostKeyChecking=no zjgump@host.docker.internal "cd /volume1/docker/nas-dashboard && /volume1/@appstore/ContainerManager/usr/bin/docker rm -f nas-dashboard-dev || true && /volume1/@appstore/ContainerManager/usr/bin/docker compose -f docker-compose.dev.yml up -d --pull never"