From 91769fe2c6b06201409100e41c0b6be26a8b081b Mon Sep 17 00:00:00 2001 From: "Gan, Jimmy" Date: Sun, 17 May 2026 19:02:07 +0800 Subject: [PATCH] fix: use network_mode:none in compose override for Docker 24 compat Docker Compose v2.20.1 still tries to connect external networks during container creation even with networks:[]. Switch to network_mode:"none" to fully prevent compose from touching networks, then connect them manually after container creation. Co-Authored-By: Claude Opus 4.7 --- .gitea/workflows/deploy-dev.yml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/.gitea/workflows/deploy-dev.yml b/.gitea/workflows/deploy-dev.yml index dc66ef2..47460b8 100644 --- a/.gitea/workflows/deploy-dev.yml +++ b/.gitea/workflows/deploy-dev.yml @@ -235,13 +235,12 @@ jobs: docker network create nas-dashboard_internal fi - # Create compose override that strips networks (Docker 24 compose - # fails to create the container when it can't connect networks). + # Create compose override with network_mode: none (Docker 24 compose + # fails to create containers when it can't connect external networks). # We connect networks manually after container creation. echo 'services:' > /tmp/docker-compose.ci-override.yml echo ' dashboard-dev:' >> /tmp/docker-compose.ci-override.yml - echo ' networks: []' >> /tmp/docker-compose.ci-override.yml - echo 'networks: {}' >> /tmp/docker-compose.ci-override.yml + echo ' network_mode: "none"' >> /tmp/docker-compose.ci-override.yml # Deploy without networks in compose docker compose -f docker-compose.dev.yml -f /tmp/docker-compose.ci-override.yml -p nas-dashboard-dev up -d --pull never