Just recently discovered Silverblue/Toolbox and I really love the general idea about a stable/robust/immutable base OS, and easily spun up (throw away) containers for experimental development etc.
However, after some intial tinkering, what I don’t understand is why you are able to write to any file or subdirectory in the the HOME directory from a toolbox. I mean, what is the point of isolation if any software you install in a toolbox can modify your home dir content? What I (naivley) expected was something more like this:
HOME dir content would (by default) be read-only from within a toolbox.
- I want my general configuration settings (nano, git) to work also in toolbox.
Any files I create or modifiy from a toolbox, under HOME, should be copied (or superimposed) onto a local toolbox “HOME” dir.
- In case I want to override my usual setting s for a given toolbox.
Ability to specify subdirectories under HOME, that a given toolbox can have full read/write acces to, when creating a new toolbox.
Of course these are my personal expectations, and other people will probably have other ones, but having found no clear description/specification of the toolbox design intentions I found it quite confusing and frankly a bit demotivating (at the moment) to invest more time into. I think it would be really great for better/wider adoption if the designers of toolbox would invest some time in explaining the roadmap and how they think it should ideally work/behave when finalized. Don’t mean to be negative, love your work, but would appreciate some more communication on the design intents.