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

fix: just restart container instead of recreating
Deploy Dashboard (Dev) / deploy-dev (push) Successful in 3m14s
Details
Run Tests / Backend Tests (push) Failing after 1m35s
Details
Run Tests / Test Summary (push) Has been cancelled
Details
Run Tests / Frontend Tests (push) Has started running
Details

Browse Source 
Docker restart will use the new image that was just built.
Avoids all the network reconnection issues from recreating the container.
Simple and proven to work.
This commit is contained in:
Gan, Jimmy
2026-04-04 02:18:26 +08:00
parent 431e2c0a5f
commit 8514d5ea4b
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy-dev.yml
+2 -3
View File
@@ -64,6 +64,5 @@ jobs:
- name: Deploy dev - name: Deploy dev
run: | run: |
export DOCKER_API_VERSION=1.43 export DOCKER_API_VERSION=1.43
# Execute deploy script on NAS host directly (not from workflow container) # Just restart the container - it will use the new image
# This avoids Docker-in-Docker network connection issues docker restart nas-dashboard-dev
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"