Documentation
¶
Overview ¶
Package contentstore holds the pieces shared by the readers of a local content bundle -- a hauler store, a zarf package -- so that two readers of the same OCI layout cannot drift apart in how they open it or how they key an image reference.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func CanonicalImageRef ¶
CanonicalImageRef puts an image reference into the one spelling two equal references share, so that a bundle is indexed and searched by the same key.
Both bundle formats record what they collected under the registry's canonical host: an image added as docker.io/rancher/pause:3.10 comes back as index.docker.io/rancher/pause:3.10, which is the same image under a name a distro definition does not use. The same split applies to an official image, where docker.io/nginx, nginx and docker.io/library/nginx are one reference written three ways. A reference that will not parse is keyed as it was written -- it would not have matched anything anyway, and failing the lookup beats failing the open.
func FileRef ¶
FileRef is where the file declared as coming from source lives in a mirror under target.
It is the one rule a writer and a reader of a mirrored file both apply, which is what lets a reader recompute a reference instead of discovering it -- a registry offers a repository catalogue and per-repository tags, never one annotated index the way a hauler store or a zarf package does, so there is nothing to walk and nothing to match against.
The name carries the file's basename so a repository listing is legible to a person, and the tag is a digest of the whole source so it is correct. Keying on the basename alone would be wrong rather than merely ugly: every rke2 and etcd release archive is named the same across versions, so one version's file would be served for another's.
func LayoutFS ¶
LayoutFS presents a directory as an OCI image layout, serving the oci-layout marker from memory when the directory has none.
A live hauler store is a complete layout except for that marker -- hauler writes one only when saving an archive. The reader needs it (oras refuses a layout without one) and must not create it, because cargoship was asked to read the operator's store, not to modify it. So it is supplied here instead, for the lifetime of the read.
A zarf package's images/ directory normally does carry the marker, because zarf writes that layout through oras, which creates one. The fallback below defers to a real file whenever there is one, so wrapping both readers in this costs nothing and leaves neither depending on a marker it did not write.
func Unpack ¶
Unpack makes the content bundle at path readable as a directory, returning the directory to read and the temporary directory the caller must remove when it is done -- which is empty when path was already a directory, because an operator's own store is never written to or removed.
It is the one place a bundle is decompressed, so that deciding which format a bundle is can be a stat against the unpacked tree rather than a second pass over the archive.
Types ¶
This section is empty.