What gets preserved from the previous deployment in a rpm-ostree rebase?

I’ve been trying to use atomic systems since forever and only now I am giving it a serious try. Been using Fedora Kinoite in the last few days trying to do things the way the docs recommend.

I rebased to a custom image built from blue-build, an independent project that started with universal blue, but I realized I prefer to stay upstream so I rebased again to regular Fedora Kinoite.

I guess my question is: do any files get carried over from the custom image? I haven’t done any configuration change on the OS, not even the writable parts, like /etc and /var (well except /var/home but I guess that’s obvious).

I’m only asking this because when I did another rebase before to a universal blue image (bazzite), when I came back, there was a bazzite/ directory under /, with directories inside. I appreciate any answers. Thanks for your time reading!

When rebasing within the same remote, the rebase works similarly to an upgrade, preserving /etc changes, layered packages, etc.

However, given that rebasing between custom images and Fedora images is not officially supported, the outcomes are not always predictable, just as in your case with Bazzite. Nevertheless, the fact that you’ve found a /bazzite folder on your system IMO shows the system is working as expected, given that / is mounted from fstab, whereas different parts of the OS image deployment are mounted/bind-mounted later during the boot process.

If you don’t want to go through the hassle of reinstalling Kinoite, you could diff compare the /etc/ contents of the current deployment with the ones from a fresh install, to make sure no relevant config files have been altered.

I have only rebased between Fedora images, others having rebased between Fedora and non-Fedora images might join in to share their experiences.

2 Likes