fix: start-core missing cell-network creation breaks fresh install

make start-core (called by install.sh step 6) used $(DCF) which includes docker-compose.services.yml — that file declares cell-network as external:true. On a fresh machine the network doesn't exist yet, so compose up failed with "network cell-network declared as external, but could not be found". Fix: add the same network-create idempotency guard that start and update already have. Also add 26 regression tests (test_install_process.py) that verify install.sh structure and that all start-* targets using DCF create the network before running compose up. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-08 01:07:00 -04:00
parent 69862331e7
commit e4c80149f4
2 changed files with 246 additions and 0 deletions
@@ -222,6 +222,8 @@ build-webui:

 start-core:
 	@echo "Starting core services (caddy, dns, wireguard, api, webui)..."
+	@docker network inspect cell-network >/dev/null 2>&1 || \
+	  docker network create --driver bridge --subnet "$${CELL_NETWORK:-172.20.0.0/16}" cell-network
 	PUID=$$(id -u) PGID=$$(id -g) $(DCF) --profile core up -d --build
 	@echo "Core services started. Run 'make start' to also bring up optional services."