Current zot sync configuration specifies what images with what tags to be pulled from a remote repo.
Each OCI image and the specified tag is copied locally, but not other tags which may be pointing to the same image manifest.
This task tracks copying all tags pointing to the same manifest which is copied by zot sync.
For example, let's say we have an image called "service" which has the following tags:
1.0.0 which point to manifest A.
latest and 1.0.1, which point to manifest B
If the zot configuration in the local repo specified only the service image with tag latest, only the tag latest would show up in the local registry after the sync is over.
Since both latest and 1.0.1 point to manifest B, I would like to copy the tag 1.0.1 as well.
This way I can be sure I always have the latest version locally, but I can also identify it using a semantic version tag.
This feature track the sync feature pulling all tag for manifest B if at least one of them is specified in the zot config.
Current zot sync configuration specifies what images with what tags to be pulled from a remote repo. Each OCI image and the specified tag is copied locally, but not other tags which may be pointing to the same image manifest. This task tracks copying all tags pointing to the same manifest which is copied by zot sync.
For example, let's say we have an image called "service" which has the following tags:
1.0.0
which point to manifestA
.latest
and1.0.1
, which point to manifestB
If the zot configuration in the local repo specified only theservice
image with taglatest
, only the taglatest
would show up in the local registry after the sync is over.Since both
latest
and1.0.1
point to manifestB
, I would like to copy the tag1.0.1
as well. This way I can be sure I always have the latest version locally, but I can also identify it using a semantic version tag.This feature track the sync feature pulling all tag for manifest
B
if at least one of them is specified in the zot config.