dep-bound-docker-image-bloat-not-worth-rebuilding

Large MCP server images (graphiti 5.65GB = Neo4j+FalkorDB+graphiti-core, mirofish 5.8GB = ML deps, oracle-hermes 4.72GB = Playwright+Chromium) appear bloated but docker history confirms the size is genuine required dependencies. Rebuilding with multi-stage or slim base risks dependency breakage for marginal disk savings. Audit with docker history before declaring an image a rebuild candidate.

Related

• dep-bound-images-graphiti-mirofish-hermes-not-optimizable
• graphiti
• docker
• openclaw
• playwright
• dep-bound-image-bloat-not-worth-multi-stage-optimization