From f34e2b1a4bb2e6918422ac3c6bd85dec2dfc91ee Mon Sep 17 00:00:00 2001 From: dispensable <3339663+dispensable@users.noreply.github.com> Date: Wed, 16 Oct 2024 17:55:20 +0800 Subject: [PATCH] Update docs/articles/mirroring.md Co-authored-by: Andrei Aaron --- docs/articles/mirroring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/articles/mirroring.md b/docs/articles/mirroring.md index 1c22810..1ea91ed 100644 --- a/docs/articles/mirroring.md +++ b/docs/articles/mirroring.md @@ -4,7 +4,7 @@ A key use case for zot is to act as a mirror for upstream registries. If an upstream registry is OCI distribution-spec conformant for pulling images, you can use zot's `sync` feature to implement a downstream mirror, synchronizing OCI images and corresponding artifacts. Because synchronized images are stored in zot's local storage, registry mirroring allows for a fully distributed disconnected container image build pipeline. Container image operations terminate in local zot storage, which may reduce network latency and costs. -> :warning: Because zot is a OCI-only registry, any upstream image stored in the Docker image format is converted to OCI format when downloading to zot. In the conversion, some non-OCI attributes may be lost. Signatures, for example, are removed due to the incompatibility between formats. Due to the OCI conversion, the image digest may change, and pulling with @ will not work as expected. +> :warning: Because zot is a OCI-only registry, any upstream image stored in the Docker image format is converted to OCI format when downloading to zot. In the conversion, some non-OCI attributes may be lost and the image digest will change. Pulling with @ will not work as expected. Signatures, for example, are removed due to the mismatch between the old and the new digests. ## Mirroring modes