Hotfix for v44.40. Phase 276 left the legacy-compat compose networks-only (auth/tor services removed), but docker compose up does not create a top-level network when there are no services → livinity_main_network was never created → every installed app failed to start (external: livinity_main_network ... could not be found).
Fix: appEnvironment('up') now creates the network explicitly + idempotently (docker network create --subnet 10.21.0.0/16 livinity_main_network) before the compose up. Reproduced and verified the fix in a Linux/docker environment.
If a box is already on v44.40 and apps are down, the manual recovery is:
docker network create --subnet=10.21.0.0/16 livinity_main_network && sudo systemctl restart livos
— or just Update to v44.41.
🤖 Generated with Claude Code
Full Changelog: v44.40...v44.41