fix: use nsenter to run deploy in host network namespace

2026-04-04 10:02:43 +08:00
parent a401ba677c
commit 89d0b8d341
1 changed files with 9 additions and 5 deletions
@@ -13,6 +13,10 @@ concurrency:
 jobs:
  deploy-dev:
    runs-on: ubuntu-latest
+    container:
+      volumes:
+        - /var/packages/ContainerManager/target/usr/bin/docker:/usr/bin/docker
+        - /volume1/docker/nas-dashboard:/nas-dashboard
    steps:
      - name: Checkout exact commit
        run: |
@@ -54,12 +58,12 @@ jobs:
      - name: Build dev image
        run: |
          export DOCKER_API_VERSION=1.43
-          DOCKER_BUILDKIT=0 /volume1/@appstore/ContainerManager/usr/bin/docker build --cache-from nas-dashboard-dev:latest -t nas-dashboard-dev:latest dashboard/
+          DOCKER_BUILDKIT=0 docker build --cache-from nas-dashboard-dev:latest -t nas-dashboard-dev:latest dashboard/
      - name: Sync runtime compose file
-        run: cp dashboard/docker-compose.dev.yml /volume1/docker/nas-dashboard/docker-compose.dev.yml
+        run: cp dashboard/docker-compose.dev.yml /nas-dashboard/docker-compose.dev.yml
      - name: Deploy dev
        run: |
          export DOCKER_API_VERSION=1.43
-          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
+          # Use nsenter to run in host network namespace to avoid Docker-in-Docker network limitations
+          nsenter -t 1 -n docker rm -f nas-dashboard-dev || true
+          nsenter -t 1 -n docker compose -f /volume1/docker/nas-dashboard/docker-compose.dev.yml up -d --pull never