Build Fedora IoT using rpm-ostree unified core
Upstream rpm-ostree development is now focused on "unified core" mode, with plans to deprecate the previous mode in the future. Fedora IoT is the last rpm-ostree based Fedora edition using this older, soon to be deprecated mode with SilverBlue and Kinoite making the change in Fedora 39. This change will align IoT with the other ostree-based editions in Fedora.
- Targeted release: Fedora Linux 40
- Last updated: 2024-02-08
- Discussion thread
- FESCo issue: #3161
- Tracker bug: #2263306
- Release notes tracker: <will be assigned by the Wrangler>
To learn about the differences between unified core and the previous mode, please read the upstream issue. The main advantage is that it is stricter and safer, while enabling some post processing steps to happen during or after the image build. In addition, unified core support is required for bootupd integration in Fedora IoT and to align with other rpm-ostree editions in Fedora.
Related changes (already complete):
Benefit to Fedora
The previous mode in rpm-ostree is not maintained anymore, less tested and thus prone to bugs. Moving to unified core will align IoT with what is used to build Fedora CoreOS, SilverBlue and Kinoite as well as benefit from the additional testing those editions receive. Making the change in IoT should also reduce the maintenance burden from the rpm-ostree project as they will be able to remove the old code. Unified core makes composes work the same on the server side as the client side and makes them safer by more strictly confining scriptlet execution.
- Proposal owners: Testing with the new mode to ensure there are no regressions.
- Other developers: N/A
- Release engineering: #11815
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A
- Alignment with Community Initiatives: N/A
- There will be no impact to end users, upgrades will work the same as previous releases
How To Test
- Upgrade to Fedora 40 IoT Edition or deploy a new installation.
- There will be no impact to users.
- Contingency mechanism: Revert to older non-unified core mode.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change)
N/A (not a System Wide Change)