oci-references

Description#

The command line client supports a special notation scheme for specifying references to instances of oci like registries. This allows for specifying references to any registry supported by the OCM toolset that can host OCI artifacts. As a subset the regular OCI artifact notation used for docker images are possible:

[+][<type>::][./][<file path>//<repository>[:<tag>][@<digest>]

[<type>::][<json repo spec>//]<repository>[:<tag>][@<digest>]

[<type>::][<scheme>:://]<domain>[:<port>/]<repository>[:<tag>][@<digest>]

<docker library>[:<tag>][@<digest>]

<docker repository>/<docker image>[:<tag>][@<digest>]

Besides dedicated artifacts it is also possible to denote registries as a whole:

[+][<type>::][<scheme>:://]<domain>[:<port>]

[+][<type>::]<json repo spec>

[+][<type>::][./]<file path>

The optional + is used for file based implementations (Common Transport Format) to indicate the creation of a not yet existing file.

The type may contain a file format qualifier separated by a + character. The following formats are supported: directory, tar, tgz

Examples#

ghcr.io/mandelsoft/cnudie:1.0.0

See Also#