artifacts

Usage#

ocm transfer artifacts [<options>] {<artifact-reference>} <target>

Options#

  -h, --help          help for artifacts
      --repo string   repository name or spec
  -R, --repo-name     transfer repository name

Description#

Transfer OCI artifacts from one registry to another one. Several transfer scenarios are supported:

• copy a set of artifacts (for the same repository) into another registry
• copy a set of artifacts (for the same repository) into another repository
• copy artifacts from multiple repositories into another registry
• copy artifacts from multiple repositories into another registry with a given repository prefix (option -R)

By default, the target is seen as a single repository if a repository is specified. If a complete registry is specified as target, option -R is implied, but the source must provide a repository. THis combination does not allow an artifact set as source, which specifies no repository for the artifacts.

Sources may be specified as

• dedicated artifacts with repository and version or tag
• repository (without version), which is resolved to all available tags
• registry, if the specified registry implementation supports a namespace/repository lister, which is not the case for registries conforming to the OCI distribution specification.

If the repository/registry option is specified, the given names are interpreted relative to the specified registry using the syntax

<OCI repository name>[:<tag>][@<digest>]

If no –repo option is specified the given names are interpreted as extended OCI artifact references.

[<repo type>::]<host>[:<port>]/<OCI repository name>[:<tag>][@<digest>]

The –repo option takes a repository/OCI registry specification:

[<repo type>::]<configured name>|<file path>|<spec json>

For the Common Transport Format the types directory, tar or tgz are possible.

Using the JSON variant any repository types supported by the linked library can be used:

• ArtifactSet: v1
• CommonTransportFormat: v1
• DockerDaemon: v1
• Empty: v1
• OCIRegistry: v1
• oci: v1
• ociRegistry

Examples#

$ ocm oci artifact transfer ghcr.io/mandelsoft/kubelink:v1.0.0 gcr.io
$ ocm oci artifact transfer ghcr.io/mandelsoft/kubelink gcr.io
$ ocm oci artifact transfer ghcr.io/mandelsoft/kubelink gcr.io/my-project
$ ocm oci artifact transfer /tmp/ctf gcr.io/my-project

See Also#

• ocm transfer — Transfer artifacts or components