Hi, this is to raise awareness of an effort we're driving from the Fedora CoreOS side here: "ship quay.io/coreos/fedora-coreos" at https://github.com/coreos/fedora-coreos-tracker/issues/812
Which builds on a bidirectional bridge between ostree and container images that lives here: https://github.com/ostreedev/ostree-rs-ext/#module-container-encapsulate-ostree-commits-in-ocidocker-images The technology applies to any editions using (rpm-)ostree. As of: https://github.com/coreos/rpm-ostree/releases/tag/v2021.7 rpm-ostree now natively supports both: `rpm-ostree ex-container export` to convert an ostree commit into a container image (which is just a proxy for the ostree-rs-ext code), as well as e.g. `rpm-ostree rebase --experimental docker://quay.io/cgwalters/fcos:latest` which converts the system to track an "ostree-container" image as a base. In other words, this uses containers as a native transport "on the wire" instead of ostree. One way I like to talk about this effort in *combination* with the cliwrap effort (also just posted) is that one can describe us as supporting "image based dnf for host updates", in other words you type `yum update` and it pulls and updates from a container image for the host. If you're interested, please check out the thread above linked which contains a fair amount of discussion on this, as well as the issues list here: https://github.com/ostreedev/ostree-rs-ext/issues which touches on things like "can/how can we support derivation" etc. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
