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?
Please don’t conflate stuff.
On Fedora Atomic[1], it’s possible to:
/etc/fstab. Heck, the same applies to everything under/etc. The only difference being that a pristine copy is kept at/usr/etcAND the fact that any changes to/etcare being tracked. Said changes can be accessed withostree admin config-diff.False. Again.
While I agree that it’s a very sane recommendation to the technologically inept, it would be a huge disservice to suggest it can’t handle more advanced workloads. Because, quite frankly, there’s very little it actually fails at. And most of its user base would vouch for this. And that list of restrictions/limitations is becoming smaller as we speak…
And probably most distros that are -perhaps erroneously- referred to as “immutable”, though the finer details might be different. ↩︎
I never said it was impossible, I said it is not for the op. The simple fact they don’t see an apparent way to install simple tools or modify fstab would be for me unacceptable, I prefer freeballing my OS, thank you very much. I simply assumed op was more like me and less like you.
The terminal motd tells you exactly how to use the packages involved when you open it.