On Wed, Nov 24, 2021 at 1:20 AM Ben Cotton <bcotton(a)redhat.com> wrote:
https://fedoraproject.org/wiki/Changes/OstreeNativeContainer
== Summary ==
Enhance the (rpm-)ostree stack to natively support OCI/Docker
containers as a transport and delivery mechanism for operating system
content.
This is the basis of
https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md
== Owner ==
* Name: [[User:walters| Colin Walters]]
* Email: walters(a)verbum.org
== Detailed Description ==
Having the Fedora ecosystem (from users to release engineering)
maintain tooling that operates on all three of "container images",
RPMs, and OSTree updates is a maintenance burden.
This proposes that:
* The ostree stack is enhanced to support
encapsulating/unencapsulating ostree commits as OCI/Docker images
(DONE)
* rpm-ostree is updated to consume this, while still supporting all
its current features (e.g. per-machine package layering) (DONE)
* We ship e.g. `quay.io/fedora/coreos:stable` and
`quay.io/fedora/silverblue:36` etc.
* We support '''deriving''' new user custom images from these
images
* We enhance this tooling to
[
https://github.com/ostreedev/ostree-rs-ext/issues/69 support
chunking]
For more details, please see:
* [
https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md
CoreOS layering enhancement]
* [
https://coreos.github.io/rpm-ostree/container/ rpm-ostree container docs]
This
is a great enhancement for the OSTree world. People can use Docker hub
or quay.io as an OSTree hub to maintain different ostree-based Linux
distributions for users to rebase and try.
This function is unrelated to 'rpm' but unfortunately provided by
'rpm-ostree'.
Maybe we should provide another standalone tool so non-rpm/dnf-based
distributions can be easier to deploy.
-robin