fix: mark portfolio_net as external to resolve compose label conflict
All checks were successful
Dev Deployment (Zero Downtime) / deploy-dev (push) Successful in 16m31s

Docker Compose refused to adopt the existing portfolio_net network because
it lacked the expected com.docker.compose.network label (created outside
Compose). Mark it as external (matching the dev setup) and pre-create it
in the deployment workflow to ensure it always exists before compose up.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-23 22:46:57 +01:00
parent b162fc8a4f
commit 21513b20c4
2 changed files with 4 additions and 2 deletions

View File

@@ -113,7 +113,6 @@ volumes:
networks:
portfolio_net:
name: portfolio_net
driver: bridge
external: true
proxy:
external: true