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

fix: use network_mode:none in compose override for Docker 24 compat
Deploy Dashboard (Dev) / Backend Tests (push) Successful in 12m48s
Details
Deploy Dashboard (Dev) / Frontend Tests (push) Successful in 34s
Details
Deploy Dashboard (Dev) / Deploy to Dev (push) Failing after 1m27s
Details

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Gan, Jimmy
2026-05-17 19:02:07 +08:00
parent 9b05bd5e74
commit 91769fe2c6
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy-dev.yml
+3 -4
View File
@@ -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