dep-bound-images-graphiti-mirofish-hermes-not-optimizable
Large images for graphiti-mcp (5.65GB), mirofish (5.8GB), and oracle-hermes (4.72GB) are genuinely dep-bound: Neo4j+FalkorDB+graphiti-core, Python ML libs, and Playwright+Chromium respectively. Docker history confirms size is real dependencies, not layer waste. Multi-stage Dockerfile optimization would risk breakage for marginal gain — these sizes are accepted as baseline and should not trigger future audit alerts.
Related
- clawteam-openclaw-multi-agent-swarm-evaluation
- docker
- hermes-fork-is-package-full-rebase-not-viable
- 2026-04-04-oracle-001-self-architecture-analysis
- openclaw-patches-regress-on-upstream-filename-rotation
- dep-bound-docker-image-bloat-not-worth-rebuilding
- dep-bound-image-bloat-not-worth-multi-stage-optimization