Layerquarry
Import container image history offline, visualize layer size and estimated waste, improve cache order, and document a smaller runtime plan.
Focused field tools
Understand that deleting a file later does not remove bytes from an earlier layer.
Exclude source history, credentials, caches, outputs, and unrelated files.
Combine install and cleanup safely within the creating layer.
Copy only required runtime artifacts from a controlled builder.
Place stable dependencies before frequently changing source inputs.
Choose maintained, compatible, minimal foundations with known provenance.
Layerquarry analyzes imported history metadata and entered assumptions; it does not open arbitrary layer files, scan vulnerabilities, connect to a registry, or prove runtime compatibility. Validate the rebuilt image, packages, architecture, permissions, signatures, and application behavior in controlled CI.