Which tool is used to copy an OCI layout from a local folder to a private registry, requiring a login via Podman first?

Which tool is used to copy an OCI layout from a local folder to a private registry, requiring a login via Podman first?

• A. skopeo copy oci:/path/to/folder docker://private.repo.com/folder/name:verison
• B. skopeo copy docker://private.repo.com/folder/name:verison oci:/path/to/folder
• C. podman login; skopeo copy docker://path oci:/path/to/folder
• D. podman login; skopeo copy oci:/path/to/folder docker://private.repo.com/folder/name:verison

Answer: (A)

You’re using a tool that can move images between a local OCI layout and a remote registry. To push from a local OCI layout to a private registry, you perform a copy with the local path as the source in OCI format and the registry as the destination in Docker/registry format. Before doing the push, you authenticate to the registry (for example with podman login) so skopeo can push with the right credentials. The command pattern that matches this flow is to copy from oci:/path/to/folder to docker://private.repo.com/folder/name:version. It shows the correct source and destination schemes (oci: for a local layout, docker:// for the registry) and the tag naming for the registry location. The login step is a prerequisite, usually run beforehand (podman login private.repo.com), so the operation can succeed. The other options either reverse the direction (copying from the registry to a local OCI layout), use the wrong source/destination combination, or mix in login in a way that doesn’t reflect the required direction of the push.

You’re using a tool that can move images between a local OCI layout and a remote registry. To push from a local OCI layout to a private registry, you perform a copy with the local path as the source in OCI format and the registry as the destination in Docker/registry format. Before doing the push, you authenticate to the registry (for example with podman login) so skopeo can push with the right credentials.

The command pattern that matches this flow is to copy from oci:/path/to/folder to docker://private.repo.com/folder/name:version. It shows the correct source and destination schemes (oci: for a local layout, docker:// for the registry) and the tag naming for the registry location. The login step is a prerequisite, usually run beforehand (podman login private.repo.com), so the operation can succeed.

The other options either reverse the direction (copying from the registry to a local OCI layout), use the wrong source/destination combination, or mix in login in a way that doesn’t reflect the required direction of the push.