Expose the Unexplained Megabytes in a Container Image

How to Use This Tool

Subtract known base, dependency and application layers from the final image. Calculate unallocated Docker image size after base image, dependency and application layers for an optimization audit.

The failure Docker Layer Size is designed to catch

Deleted files can remain in earlier layers, so the unexplained remainder often points to cache, package-manager or build-artifact leakage. The boundary is the job stated in Expose the Unexplained Megabytes in a Container Image; Docker Layer Size is not intended to score or transform a different workflow.

The Docker Layer Size input contract

The fields used for this specific operation are Final image size MB, Base image layers MB, Dependency layers MB, Application layers MB. Keep the source values beside the Docker Layer Size result, because replacing the original would remove the evidence needed to reproduce or reverse the operation.

• For Docker Layer Size, Final image size MB starts at 1200 in the worked case; replace that example with the matching source value.
• For Docker Layer Size, Base image layers MB starts at 400 in the worked case; replace that example with the matching source value.
• For Docker Layer Size, Dependency layers MB starts at 500 in the worked case; replace that example with the matching source value.
• For Docker Layer Size, Application layers MB starts at 100 in the worked case; replace that example with the matching source value.

Worked result for Docker Layer Size

The executable case called Default decision scenario expects out: 200.0. Verify that observation before entering real material, and then change one Docker Layer Size field at a time so an unexpected direction or formatting change can be traced to a specific input.

Reading the Docker Layer Size output

It combines final image size mb, base image layers mb, dependency layers mb and application layers mb into one decision result using the formula explained on the page. Apply that answer only when Final image size MB, Base image layers MB, Dependency layers MB, Application layers MB describe the same scope and format as the worked operation. If the source uses different units, quoting, nesting, timing or account rules, a plausible-looking Docker Layer Size output is not sufficient validation.

Assumptions attached to Docker Layer Size

• Docker Layer Size assumes that all inputs describe the same unit or reporting period unless the field explicitly says otherwise.
• Docker Layer Size assumes that the model includes only the four visible inputs and does not infer hidden platform charges.

If one of these Docker Layer Size assumptions is false, keep the result as a diagnostic rather than production or decision data, and choose an implementation that explicitly supports the missing rule.

Evidence maintained for Docker Layer Size

The recorded reference is AWS Well-Architected — cost optimization. Reopen that source when the definition, format, fee or policy behind Docker Layer Size changes; private configuration and downstream acceptance still have to be checked in the user's own system.

Where Docker Layer Size runs

The named operation executes in browser JavaScript without an ecech calculation API. For Docker Layer Size, local execution reduces transmission but does not control browser extensions, device security or the destination where the result is pasted, so sensitive inputs still require the user's normal handling rules.