fix: use docker stop/rm instead of compose down for deploy
docker compose down may have issues with external networks or project names. Use direct docker stop/rm commands instead.
This commit is contained in:
@@ -64,6 +64,8 @@ jobs:
|
|||||||
- name: Deploy dev
|
- name: Deploy dev
|
||||||
run: |
|
run: |
|
||||||
export DOCKER_API_VERSION=1.43
|
export DOCKER_API_VERSION=1.43
|
||||||
# Stop and remove old container, then create with new image
|
# Stop and remove old container if it exists
|
||||||
docker compose -f /nas-dashboard/docker-compose.dev.yml down || true
|
docker stop nas-dashboard-dev 2>/dev/null || true
|
||||||
|
docker rm nas-dashboard-dev 2>/dev/null || true
|
||||||
|
# Create new container
|
||||||
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
|
||||||
|
|||||||
Reference in New Issue
Block a user