You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when restoring from an existing OCI layout, the OCI store will index the predecessor relationships for all the manifests in index.json, which are tagged manifests.
However, the predecessors of manifests are usually not tagged and are not present in index.json.
As a result, these predecessors will not be indexed, and they cannot be discovered by the Predecessors() function of the OCI store. This blocks scenarios like extended-copying a graph from an OCI store that is restored from an existing OCI layout to other Targets.
The text was updated successfully, but these errors were encountered:
Wwwsylvia
changed the title
OCI store should support discovering predecessors that are not in index.json
OCI store should support discovering predecessors that are not tagged
Oct 11, 2022
The implementation of zot gives an idea that we can store un-tagged manifests in the index.json so that predecessors can be indexed without a tag schema.
…esolve()` (#385)
1. Support discovering predecessors that are not tagged
2. Support resolving a manifest by its digest
3. Support resolving a blob by its digest
Resolves: #342
Signed-off-by: Lixia (Sylvia) Lei <[email protected]>
Currently, when restoring from an existing OCI layout, the OCI store will index the predecessor relationships for all the manifests in
index.json
, which are tagged manifests.However, the predecessors of manifests are usually not tagged and are not present in
index.json
.As a result, these predecessors will not be indexed, and they cannot be discovered by the
Predecessors()
function of the OCI store. This blocks scenarios like extended-copying a graph from an OCI store that is restored from an existing OCI layout to other Targets.The text was updated successfully, but these errors were encountered: