This is a tracking bug for Change: ostree native containers / CoreOS layering
For more details, see: https://fedoraproject.org/wiki/Changes/OstreeNativeContainer
Enhance the (rpm-)ostree stack to natively support OCI/Docker containers as a transport and delivery mechanism for operating system content.
If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
The FCOS development and discussion is very Github oriented, not Bugzilla oriented. I'm going to try to bridge these two worlds by periodically summarizing important things here.
But I've created a "coreos-layering" label on the FCOS tracker: https://github.com/coreos/fedora-coreos-tracker/issues?q=is%3Aissue+is%3Aopen+label%3Aarea%2Fcoreos-layering
And I'd like to try to keep track of discussions there.
Some important recent updates:
- https://github.com/coreos/fedora-coreos-pipeline/pull/457/commits/ffa2b9b78b46bb5b5c593c589d5219b2800e2816 landed
which means production Fedora CoreOS builds also update a container image (that is GPG signed!)
- rpm-ostree (in git main) now directly supports package installs *inside* a container build
- A *lot* of work happening on the ostree side, bug fixes like https://github.com/ostreedev/ostree-rs-ext/issues/211 etc.
- https://coreos.github.io/rpm-ostree/container/ and https://coreos.github.io/rpm-ostree/layering/
are both useful reference points, and have been updated too.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 36 development cycle.
Changing version to 36.
Today we reached the Code Complete (testable) milestone in the F36 schedule: https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
All code for this change should be complete enough for testing. You can indicate this by setting the bug status to MODIFIED. (If the code is fully complete, you can go ahead and set it to ON_QA.)
If you need to defer this Change to F37, please needinfo bcotton.
We've gotten a lot done for this, but I think probably what makes the most sense is to re-brand it as "Preview" or so. In particular I don't think we're quite ready to commit to supporting the current container build model into the indefinite future. I have a tracker for that here https://github.com/ostreedev/ostree-rs-ext/milestone/2
Nothing we've shipped is going to eat your root filesystem or anything like that - I just want to get more people to try it out before we call everything 100% stable.
Does that make sense? Is there any standard verbiage to use for this for the Change page?
There's no standard verbiage. You might want to edit the wiki page to add the word preview and indicate how users can opt-in (if that's relevant). Please also note that in the release notes issue: https://pagure.io/fedora-docs/release-notes/issue/777
Alternatively, we can move this to F37 and just have the preview rollout happen more quietly in F36.
(Also setting the status to MODIFIED since it appears that it's in a testable state at this point)
We have reached the 'Change complete (100% complete)' deadline in the Fedora Linux 36 release schedule.
At this time, all Changes should be fully complete. Indicate this by setting this tracking bug to ON_QA.
If you need to defer this Change to a subsequent release, please needinfo me.
I've updated the change page to note the preview status. But significant code is shipping and ready to try!
Awesome, thanks! I added a comment to the release notes issue as well.
F36 was released today. If this Change did not land in the release, please notify bcotton as soon as possible.