So which one of the options do you want to set specifically for your home or var submodule? I don’t see what’s missing in your case.
Looks like we need to look into this. Can you file an issue in the bootc tracker as this should be impacting all bootc variants? Thanks!
Jumping in to say this common issue is also effecting me on F43.
I didn’t spend much time on it, but all the bugs are still open, so I updated the description to indicate it affects F42+ (instead of just F42). Thanks for your ping.
@siosm So you didn’t transfer ro option from fstab?
I suppose you can do it, but it’s read-only anyway because of composefs. Check it with findmnt | grep --extended-regexp '^/'. See also Fedora Atomic Desktops filesystem layout.
I asked because Anaconda still inserted ro in fstab, so either it’s excessive or there is some difference here.
See:
1 Like
With Atomic Desktops, the root file systems is mounted by ostree and not by any entry in the fstab file. It is thus hardcoded that the root file system is read-only except for the /etc and /var part of it. That is what makes it an atomic desktop.
1 Like
Generic options (such as noatime) do not span this way to the other subvolumes.
What is the best way to set them globally?
Editing fstab for every (btrfs) mount seems hacky.
well, i applied the solution:
$ sudo rpm-ostree kargs --delete=rootflags=subvol=root --append=rootflags=subvol=root,compress=zstd:1
and now the system is broken. silverblue 44 updated.
the result looks like this
is there a fix beyond restore from backup ?
You should be able to rollback to a previous deployment from the Grub menu.