Which command publishes a locally built S2I builder image to quay.io?

Which command publishes a locally built S2I builder image to quay.io?

• A. docker push quay.io/<user>/<name>
• B. oc import-image <name> --from quay.io/<user>/<name>
• C. skopeo copy docker://quay.io/<user>/<name> containers-storage:localhost/<name>
• D. sudo skopeo copy containers-storage:localhost/<name> docker://quay.io/<user>/<name>

Answer: (D)

When publishing a locally built S2I builder image to quay.io, you copy the image from your local container storage to the remote registry. Using skopeo copy with the local storage transport as the source (containers-storage:localhost/<name>) and the registry as the destination (docker://quay.io/<user>/<name>) pushes the image directly to quay.io without needing to run a separate container daemon. Running with sudo may be necessary to access the local storage. Why this fits best: It matches the workflow of taking something built and stored locally and moving it to a remote registry. The other approaches either push from the Docker daemon when the image isn’t in Docker, import into an OpenShift image stream, or pull from quay.io back into local storage, which is the opposite of publishing.

When publishing a locally built S2I builder image to quay.io, you copy the image from your local container storage to the remote registry. Using skopeo copy with the local storage transport as the source (containers-storage:localhost/) and the registry as the destination (docker://quay.io//) pushes the image directly to quay.io without needing to run a separate container daemon. Running with sudo may be necessary to access the local storage.

Why this fits best: It matches the workflow of taking something built and stored locally and moving it to a remote registry. The other approaches either push from the Docker daemon when the image isn’t in Docker, import into an OpenShift image stream, or pull from quay.io back into local storage, which is the opposite of publishing.