48 ms·
Fedora's OSTree recently-ish started supporting using OCI containers as the content-addressed image backend in addition to their original git-like one: https:/
by gclawes 3y ago
Fedora's OSTree recently-ish started supporting using OCI containers as the content-addressed image backend in addition to their original git-like one:
https://coreos.github.io/rpm-ostree/container/ https://coreos.github.io/rpm-ostree/container/
https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable https://fedoraproject.org/wiki/Changes/OstreeNativeContainer...
- curt15 3y agoAre OCI images content-addressed?
- justincormack 3y agoYes
- pixelatedindex 3y agoWhat does content-addressed mean?
- gclawes 3y agoThe identifier for the content (image layers + manifest) is the hash of the content, and the has serves as an "address", the registry repo + tag is basically a pointer to a hash.
- pixelatedindex 3y agoThank you. Would other type of addressing be something like offset-based or address-based? Just trying to imagine different ways a file can be packed as I never gave it much thought.
- yjftsjthsd-h 3y agoI'm pretty sure it's just the difference between a file being named foo.tar.gz and (SHA-256 of the file).tar.gz[0] - the content and storage are the same, it's just that the canonical name is a hash of the contents rather than being arbitrary. [0] ex. 1324cca9ed1d8267363ef6c835ca251bd810c21c49b2acc00e02d607c95ef9ad.tar.gz