mosaicstack/stack
25
0
Fork 1
Code Issues 348 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

docs: BUILD-LOG, unused Docker networks listed before removal (Mos's ruling)

Browse Source 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
jason.woltje
2026-10-09 08:26:07 -05:00
co-authored by Claude Opus 5.5
parent 112071c74b
commit 7525431978
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
BUILD-LOG.md
+13
View File
@@ -3666,3 +3666,16 @@ Integration gate in a worktree on 2557e29d with build.patch applied (manifest e8
The trackers boot case was the one combined-tree check neither packet could run. A scratch test in the gate worktree, not committed, built a business with tracker.baseUrl and a project naming a tracker project, pointed it at S3's FakeVikunja over HTTP, and booted the real host. bootConfig emitted trackers, process.mjs loaded the adapter, and startup made 18 requests and went ready. As a pm launch, task.close on a missing task answered task-not-found after GET /tasks/999. That test moves into the S4 follow-up as a committed case.
The index was checked blob by blob against the candidate manifest before the commit. The patch's 18-digit ids are padded fixtures, and no token pattern matched.
### 2026-10-09 — Sage, unused Docker networks removed (Mos's ruling)
Before: 32 networks, 30 of them bridge, plus `host` and `none`, and 55 containers, running or stopped. Compose gates had been failing to get a subnet since 10-08, and seats were working around it with COMPOSE_PROJECT_NAME=gate2. Mos ruled in thread 1eba59e5 (AM standup, rows 38 and 39): remove bridge networks that no container references, running or stopped. Never touch `bridge`, `host`, `none` or any network a container uses. Leave volumes alone and leave `daemon.json` alone.
Method: I read every container's `NetworkSettings.Networks` (name and id) and `HostConfig.NetworkMode` from `docker inspect`, and every network's `Containers` count from `docker network inspect`. A network is removed only if all three are empty or absent for it. The 15 kept networks include `mosaic-internal`, `mosaic-public`, `mosaic-dev_default`, `jarvis-crypto_default`, `compose-audit_default`, `mosaic-mono-v1_default` and `sage-phr-ng_sage-network`. Each has no running container but is named by a stopped one, so it stays. Receipts are in `~/sage-scratch/netclean/`.
To remove, 17:
- Compose defaults: `baseline_default`, `containerization-plan_default`, `export_default`, `gate_default`, `mosaic-stack-dev-test_default`, `mosaic-stack_default`, `r5-commit_default`, `repo_default`, `s1_default`, `s1gate-e16faafd_default`, `s2b-gate_default`, `s2c-gate_default`, `s2wt_default`, `tree_default`. Compose recreates each one on the next `up`.
- Woodpecker leftovers from 10-05 and 10-06: `wp_01m47beg5ktfm8sd81e7rd5mxt_0_default`, `wp_01m47t2qfvc30gf7v17a1dt0jj_0_default`.
- `rev02r7`, created by hand on 2026-09-15 with no labels. Compose won't recreate it. Its only trace is a rev-code-02 session log from September, and no compose file or config names it.
The reference check runs again just before each removal. A network that gains a container in the meantime is skipped and reported.