jimmy/nas-tools
1
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

fix: execute docker commands on NAS host via SSH
Deploy Dashboard (Dev) / deploy-dev (push) Failing after 4m8s
Details
Run Tests / Frontend Tests (push) Has been cancelled
Details
Run Tests / Test Summary (push) Has been cancelled
Details
Run Tests / Backend Tests (push) Has started running
Details

Browse Source 
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.
This commit is contained in:
Gan, Jimmy
2026-04-04 02:13:10 +08:00
parent 2f65691e15
commit 431e2c0a5f
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy-dev.yml
+3 -4
View File
@@ -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"