How to Use This Tool
Estimate registry traffic when every target node must download the image. A rollout that is fast on warm nodes can saturate registry or site bandwidth when an entire fresh fleet downloads the same large image.
Why Image Pull Data needs more than a raw total
Compressed image size multiplied by cold nodes gives the transfer floor before retries and multiple architectures are considered. For this page, the useful comparison is total image data transferred, not whichever input happens to be largest. The Image Pull Data result answers the decision in the heading and should not be reused as a score for a different workflow.
The exact Image Pull Data formula
Total pull data equals compressed image size multiplied by nodes requiring a cold pull. The visible fields are Compressed container image size and Nodes requiring a cold pull. For Image Pull Data, read each printed unit before entry and make the values describe one transaction, cohort or reporting window. If those scopes differ, the displayed total image data transferred may be arithmetically valid but operationally meaningless.
Interpreting total image data transferred
Compare total data with registry and network capacity, reduce layers or pre-pull when a cold deployment would exceed the rollout window. The ten-percent comparison is deliberately narrow: it tests the influence of compressed container image size and is neither a forecast nor a confidence interval. Preserve the values used, their dates and the resulting decision so a later reviewer can reproduce why Image Pull Data supported the choice.
What this Image Pull Data model leaves out
This excludes cached layers, compression differences, retries, replicas on the same node, registry egress pricing and concurrent transfer speed. That is where Image Pull Data stops being trustworthy. If an excluded factor could reverse total image data transferred, extend the model explicitly or use the authoritative account system instead of hiding the factor inside an unexplained adjustment.
Evidence and independent verification
The reference reviewed for Image Pull Data is Docker Docs — Images. Docker Docs — Images supports the named definition or rule but does not supply private values for total image data transferred. Before acting on the result, reconcile the worked example with the relevant dashboard, invoice, export or measurement.
Private, reproducible calculation
Image Pull Data runs its arithmetic in the current browser tab and requests no login or API key. That keeps the Image Pull Data inputs away from the site's calculation server, while leaving the user responsible for detecting stale data or a changed platform rule. When an assumption changes, reopen Docker Docs — Images and rerun the saved Image Pull Data scenario.
Sources & assumptions
Tool Spec v2 · verified 2026-08-22. Platform rules and fees can change; the editable inputs remain authoritative for your account.
Official references
- Docker Docs — Images (checked 2026-08-22)
Model assumptions
- Every input covers the same reporting period or cohort.
- This excludes cached layers, compression differences, retries, replicas on the same node, registry egress pricing and concurrent transfer speed.
- The calculator uses only the visible fields and does not fetch account data.
