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

fix: properly recreate container on deploy
Deploy Dashboard (Dev) / deploy-dev (push) Failing after 6m18s
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 
Use 'docker compose down' then 'up' instead of --no-recreate to ensure
the new image is used and avoid network connection errors.
This commit is contained in:
Gan, Jimmy
2026-04-04 00:45:55 +08:00
parent 2c7787dced
commit e0cc38ecb5
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,7 +64,6 @@ jobs:
- name: Deploy dev - name: Deploy dev
run: | run: |
export DOCKER_API_VERSION=1.43 export DOCKER_API_VERSION=1.43
# Use --no-recreate to avoid network issues, just restart with new image # Stop and remove old container, then create with new image
docker compose -f /nas-dashboard/docker-compose.dev.yml up -d --no-recreate --pull never || \ docker compose -f /nas-dashboard/docker-compose.dev.yml down || true
# If container doesn't exist, create it
docker compose -f /nas-dashboard/docker-compose.dev.yml up -d --pull never docker compose -f /nas-dashboard/docker-compose.dev.yml up -d --pull never