AI Infrastructure
A Moved Container Tag Does Not Define the Registry Payload Kept
A moved container tag changes which manifest that name selects. It does not establish which stored manifests a collector retains. Historical Distribution v2.8.3 includes enumerated untagged manifests by default. In the fictional REG64 case, that rule marks 160 MiB of unique layer payload; its alternate untagged-removal rule marks 128 MiB. The corresponding unmarked layer candidates are 8 MiB and 40 MiB. Interpret a retention report from its actual manifest roots and shared references; neither candidate total establishes reclaimed storage.
01
Separate a tag lookup from a collector root
A registry report may show the new image selected by a training tag while saying little about the former image's retained dependencies. The missing question is which stored manifests the collector treats as roots: the starting objects whose references it marks for retention.
OCI Distribution Specification v1.1.1 defines a tag as a human-readable pointer to a manifest. A manifest can have zero, one or many tags. The OCI Image Specification v1.1.1 describes an ordinary single-platform image manifest with separate configuration and ordered layer references.
Historical Distribution v2.8.3 supplies a concrete implementation distinction. Its MarkAndSweep function enumerates repositories and their stored manifests. With RemoveUntagged false, it marks each enumerated manifest and its references without requiring a current tag. The OCI manifest implementation returns the config and layers as those references. The historical default is false.
These tagged implementation sources establish the collector behavior discussed here. The separately cited OCI editions establish definitions and API boundaries; they do not demonstrate that v2.8.3 implements every v1.1.1 feature or identify the software installed by a particular provider.
References: [OCI-D] [OCI-M] [D-GC] [D-OCI] [D-DEFAULT]
02
REG64 fixes the complete inventory before the tag moves
REG64 is a fictional reference-accounting case with one complete, stable registry and one repository. It contains exactly three valid ordinary single-platform OCI image manifests, M1, M2 and M3, and five layer blobs. All referenced objects exist, and all enumerations succeed.
The layer identities and payloads are S at 64 MiB, A at 32 MiB, B at 48 MiB, O at 16 MiB and U at 8 MiB. One MiB means 1,048,576 bytes. Each layer is stipulated to be stored once. S denotes identical content wherever referenced; these symbols are teaching identities, not real digests or API payloads.
M1 references layers S and A, plus config C1. M2 references S and B, plus C2. M3 references S and O, plus C3. Each config is distinct and exactly 1,024 bytes. Configs, manifests, storage metadata and links are separate from every layer-payload total below. Excluding them does not assign them zero physical space.
Initially, train selects M1 and rollback selects M3. M2 is already stored but untagged. A later permitted, successful repoint makes train select that existing M2; rollback continues selecting M3. All three manifest revisions and every layer and config remain stored at the final observation. No tag deletion or manifest deletion is assumed or performed.
The complete case excludes other repositories or unknown roots, concurrent changes, indexes and nested manifests, subjects, referrers, signatures, schema1 manifests, external layers, uploads in progress, legal holds and vendor lifecycle services. Host caches, unpacked images, writable layers and running readers are outside its accounting. No backend allocation, compression or replication arrangement is specified.
Both final evaluations apply historical rules mathematically to this same fixed inventory. They represent no collection run or retention-policy recommendation.
References: [U1]
03
A tag-only total can grow while stored payload stays unchanged
Before the repoint, train's per-image layer payload is S + A = 64 + 32 = 96 MiB. Rollback's is S + O = 64 + 16 = 80 MiB. Adding those per-image figures gives 176 MiB, counting S twice. Their unique layer union is S, A and O: 112 MiB.
After the repoint, train's figure becomes S + B = 64 + 48 = 112 MiB. Rollback remains 80 MiB. The sum becomes 192 MiB, again counting S twice. The current-tag unique union is now S, B and O: 128 MiB.
Thus the tagged per-image sum changes from 176 to 192 MiB, and the tagged unique union changes from 112 to 128 MiB. Neither change requires another stored layer in this case: M2 and B were already present.
Across all three stored manifests, the referenced unique layers remain S, A, B and O, totaling 64 + 32 + 48 + 16 = 160 MiB at both observations. Including the unreferenced U gives 168 MiB across all five stored layer blobs. The final 192, 128, 160 and 168 MiB figures can all be correct descriptions of different populations. The report must identify which one it means.
04
The default evaluation keeps untagged M1 and its layer A
Apply the historical default rule to the final inventory. The retained manifest roots are M1, M2 and M3. Their marked layers are S, A, B and O: 160 MiB of unique layer payload. U is the only unmarked layer, contributing 8 MiB.
The other marked content objects are the three manifests and C1, C2 and C3. The three configs contribute 3,072 bytes separately; manifest lengths and storage metadata have not been supplied. They cannot be folded into the 160 MiB layer-only figure.
M1 has lost its current train tag, but it remains an enumerated manifest. Its reference still keeps A marked. The repoint changed a tag relationship; it did not alter M1's contents or remove that manifest revision. S remains shared, and rollback's M3 independently retains O.
Consequently, a tag-only account omits A from the default retained layer set. M1 being untagged and M1 being absent from the manifest inventory are different premises. Substituting the second for the first would change the case.
05
The alternate rule changes the candidates to A and U
Hold the final stored inventory fixed and consider the explicitly alternate RemoveUntagged true branch. It checks which current tags refer to each manifest. A manifest with none is classified for deletion and skipped before its content and references are marked. An old association in a tag's history is not a match against its current link.
In REG64, M1 has no current tag, while train names M2 and rollback names M3. The retained roots for this evaluation are therefore M2 and M3. Their marked layers are S, B and O: 64 + 48 + 16 = 128 MiB.
A and U are unmarked layers, totaling 32 + 8 = 40 MiB. M1 and its distinct C1 are separately unmarked content objects; C1 contributes another 1,024 bytes outside that layer total. M2, M3, C2 and C3 remain marked.
The difference from the default layer-candidate total is 40 - 8 = 32 MiB, exactly A's payload. S does not join the candidate set because M2 and M3 still reference it. O remains referenced through rollback. These results classify the same stored objects under different root rules; they do not describe objects already removed.
06
Require the report to reconcile roots, sharing and candidates
Suppose a supplier's final report lists train at 112 MiB and rollback at 80 MiB. Those rows support the stipulated 192 MiB per-image sum. A deduplicated current-tag report can correctly return 128 MiB. Neither report alone establishes the default collector's 160 MiB marked-layer population.
Likewise, identifying the former train image as 96 MiB does not make 96 MiB an exclusive candidate. Its S layer is shared. Under the default rule, its A layer also remains marked through M1. Under the alternate rule, A supplies the additional 32 MiB candidate payload; U supplies the other 8 MiB independently of the repoint.
Ask the appointed registry provider to connect its report to the actual implementation and version, the root-selection rule, a complete manifest-and-blob inventory at the stated observation, and the references and sharing scope behind the totals. A satisfactory REG64 explanation names the marked and unmarked identities for the applicable rule and accounts for configs and manifests separately. More displayed image-size detail cannot replace that reconciliation.
The sharing scope matters because the historical collector enumerates repositories before classifying global blobs. REG64 deliberately supplies the complete registry as one repository. A report from only one repository in a larger registry would leave other references unresolved.
An unmarked payload quantity is an eligibility classification. Relating it to observed backend space requires separate storage evidence, including the actual allocation and retained copies involved. The case supplies no reclaimed-space, billing, reclaim-time or operational-success result. Collector execution, retention authority and collection safety remain decisions for the appointed registry and storage owners.
OCI Distribution v1.1.1 also permits deletion to be disabled and does not require every registry to offer tag deletion. A moved tag cannot be silently replaced with an assumed deletion action, and this historical example supplies no universal deletion or collection procedure.
07
Use the adjacent guides for their distinct storage decisions
The related Iceberg snapshot guide explains the shared reachability principle: retained references can keep superseded content needed. REG64 adds the collector's choice of roots, showing precisely why currently visible tags can underdescribe that set.
Use the container pull-size guide for compressed layers, unpacked representations and host storage. Use the Arm-versus-x86 container guide when selection involves a multi-platform index, which REG64 excludes. Use the model-registry promotion guide when the question is whether serving consumers adopted a release. The tag named rollback here is only a retained reference; its name establishes no application-recovery outcome.
08
Connect a separate equipment requirement to physical installation
If the surrounding platform project also requires server or storage equipment installed, Leviathan's rack-and-stack service and project inquiry below address that physical package. The service covers agreed equipment mounting, IT cabling, labels and physical installation records.
Share a nonconfidential equipment summary, site, released rack positions, approved IT connection requirements and the required handoff to discuss scope and availability. Registry administration, hosting, software commissioning, garbage collection and storage allocation remain with the appointed software and storage providers.
References: [L1]
09Sources
Primary sources
- [D-GC]Distribution v2.8.3: MarkAndSweep collector implementationChecked 2026-10-21. Historical manifest enumeration, conditional untagged-manifest exclusion and digest marking. REG64 restricts applicability to a complete stable inventory of ordinary flat image manifests.
- [D-TAG]Distribution v2.8.3: Tag storage and current-tag lookupChecked 2026-10-21. Tag updates the current link; Lookup compares current tag links with the requested manifest digest. These internal methods do not establish a supported tag-deletion API.
- [D-OCI]Distribution v2.8.3: OCI image-manifest referencesChecked 2026-10-21. References returns the configuration descriptor and layer descriptors for this historical ordinary-image implementation. Indexes and later subject/referrer relationships are outside the example.
- [D-DEFAULT]Distribution v2.8.3: Collector default and option bindingChecked 2026-10-21. Establishes false as the historical untagged-removal default and its binding to the collector. It is not current deployment guidance.
- [OCI-M]OCI Image Specification v1.1.1: Image ManifestChecked 2026-10-21. Separately defines the single-platform image manifest's configuration and layer descriptors. Its later artifact features are not attributed to Distribution v2.8.3.
- [OCI-D]OCI Distribution Specification v1.1.1: Definitions and Content ManagementChecked 2026-10-21. Defines tags, manifests, configs and blobs, and makes deletion support conditional. These API definitions do not specify a universal collector retention rule.
- [U1]NIST: Prefixes for binary multiplesChecked 2026-10-21. Defines one MiB as 1,048,576 bytes, distinct from decimal MB. REG64's sizes are stipulated layer payloads.
- [L1]Leviathan Systems: Rack-and-Stack and Colocation InstallationChecked 2026-10-21. Defines agreed physical equipment mounting, IT cabling, labels and handoff records.
10Related
Related Leviathan resources
Container layers: distinguish pull payload from runtime storage
Iceberg snapshots: retained references and selected dataset membership
Arm and x86 containers: identify the selected platform manifest
Model-registry promotion: trace the serving release and return scope
Rack-and-stack physical installation scope
Discuss a separate equipment installation and physical handoff
Contact
Does the surrounding project need equipment installed?
Share a nonconfidential equipment summary, site, released rack and IT connection plans, and required physical handoff to discuss a separately agreed installation scope and availability.