This is a tracking bug for Change: Enable read only /sysroot for Fedora Silverblue & Kinoite For more details, see: https://fedoraproject.org/wiki/Changes/Silverblue_Kinoite_readonly_sysroot This change is about enabling an opt-in ostree feature that re-mounts /sysroot as read only to avoid accidental changes. 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.
Today we reached the Code Complete (Testable) milestone on the F37 schedule: https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html At this time, all F37 Changes should be complete enough to be testable. You can indicate this by setting this tracker to the MODIFIED status. If the Change is 100% code complete, you can set the tracker to ON_QA. If you need to defer this Change to F38, please NEEDINFO me. Changes that have not reached at least the MODIFIED status will be given to FESCo for evaluation of contingency plans.
All code changes have been merged, ready to test.
Edit: the anaconda code change has been merged upstream. We will have to wait until it lands in a package update in Fedora.
We think this has broken ostree composes in Branched and Rawhide: https://pagure.io/releng/issue/10969#comment-810666
New PR for update logic in https://pagure.io/workstation-ostree-config/pull-request/289. New installs should still be testable as the Anaconda changes landed.
Has something about this landed recently? I do a hack in the openQA tests to change Firefox's config, where we write to the file under /ostree/deploy/fedora*/deploy/ , and this stopped working yesterday with a "Read-only file system" error. Is there a way to turn this off, or some alternative way I can write a file under /usr/lib64/firefox , which I need to do to change Firefox policies? I guess I could do the tweak in the post-install, pre-reboot phase on Silverblue, possibly...
Yes, the anaconda part of this change makes /sysroot RO and this includes the ostree repo as /ostree points to /sysroot/ostree. If this is for testing, I'd recommend using `rpm-ostree usroverlay` and then making the changes as needed, or more cleanly, creating an RPM with the file as needed installed in the correct location and then overlaying it live with `rpm-ostree install --live package.rpm`.
If you can point me to the code or a PR I can review.
I think you gave me enough to work with, thanks!
This is now fully re-enabled in Rawhide & F37. I've manually tested a Rawhide installation and an update from a non RO sysroot. I will test F37 soon.
Today we reached the Code Complete (100% complete) milestone on the F37 schedule: https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html At this time, all F37 Changes should be 100% complete. You can indicate this by setting this tracker to the ON_QA status. If you need to defer this Change to F38 please NEEDINFO me. Note that we are entering the Beta freeze. Additional package changes to complete this Change will need an approved blocker or freeze exception. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process for more information. Changes that have not reached the ON_QA status will be given to FESCo for evaluation of contingency plans.
Moving to ON_QA as this is complete for Silverblue & Kinoite. IoT has some issues that are under-investigation.
F37 was released today, so I am closing this tracker. If this Change was not completed, please notify me ASAP.