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

fix: remove stale containers unconditionally before compose

Browse Source 
Old nas-dashboard from failed runs was still running, causing the
retry path to skip (old container detected as running). Also stale
docker-socket-proxy with restart:unless-stopped caused compose
conflict. Fix by force-removing both before compose.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Gan, Jimmy
2026-05-26 00:09:53 +08:00
parent ea329a81e2
commit 9624304bd4
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy.yml
+2 -1
View File
@@ -251,7 +251,8 @@ jobs:
# Stop and remove old containers to force recreate with new image. # Stop and remove old containers to force recreate with new image.
# External networks (gitea_gitea, nas-dashboard_internal) are preserved. # External networks (gitea_gitea, nas-dashboard_internal) are preserved.
docker compose -f /nas-dashboard/docker-compose.yml down 2>/dev/null || true docker compose -f /nas-dashboard/docker-compose.yml down 2>/dev/null || true
echo "Old containers stopped" docker rm -f docker-socket-proxy nas-dashboard 2>/dev/null || true
echo "Old containers stopped and removed"
# --pull never prevents overwriting the image we just built # --pull never prevents overwriting the image we just built
docker compose -f /nas-dashboard/docker-compose.yml up -d --pull never 2>&1 || true docker compose -f /nas-dashboard/docker-compose.yml up -d --pull never 2>&1 || true