Looks great! Some stuff you might find interesting:
I never found out what my system was busy with, but when I tried again a few minutes later, the error was gone.
rpm-ostree automatically downloads new metadata in the background, which you can see with an
rpm-ostree status. If you want to do something without waiting for that to finish, run
Why the vim flatpak maps the home directory onto the container correctly, but not the rest of the filesystem, I never found out. In the end, I ditched vim-as-a-flatpak, and installed vim as a layered package.
This is simply because Flatpak has its own rootfs, and inside things are expected to be laid out in a certain way. Outside of
/home, other host directories should be in
/run/host/, e.g. your host
/etc is under
Unfortunately the VirtualBox package didn’t play nice with my read-only filesystem.
Another note: AFAIK the VirtualBox package doesn’t build on Silverblue, not sure if the recent akmods changes would fix that.
If you’ve used Chrome on Linux
As a side note, you seem to be doing well with Chromium, but if you wanted vanilla Chrome, I created a not-really-a-Flatpak wrapper, which basically appears as a Flatpak but actually runs Chrome on the host, which is what I’m using for now until I can get a true Chrome Flatpak (which I am working on, it’s just kinda messy).