I’ve read that containers are preferred for development, but they aren’t persistent and it doesn’t seem like files such as /etc/fstab can be accessed through them when running distrobox (I enjoy editing such files using vim).
It’s also a bit annoying having to enter a specific container to run something like btop.
Are you supposed to layer them with rpm-ostree?
That’s the neat part - You don’t! (unless you want incredibly long update times as every new util is a new overlay!)
Incredibly long update time? Yeah… No. Definitely not something in had any issues with due to layered packages.
And to create your own image, you need half the repo as dependency and a 20 steps chain.
Not in my experience. Though, I suppose I have to thank BlueBuild for the heavy lifting. It’s not even restrictive either, even big[1] projects like secureblue depend on it.
relatively speaking ↩︎