Too bad I never named the character.
I'm still configuring my #alpinelinux + #cosmic desktop, and I realize I didn't want to install git in the main user-land on that computer, I'm being extra paranoid - and kind of petty. So I did whatever sane person would do:
- install #podman
- configure podman to be #rootless
- install #crun because rootless is not exactly what I really want
- install #toolbx
- install #git inside that isolated container
- profit
How do you people use #distrobox or #toolbx?
Do you create one container per project/topic you are working on?
Or do you have your #containers named like their base image and install your stuff just wherever it is easiest?
Do you reuse your home dir for each container or create a private one for each?
Do you have a "default" container or do you work on the host if you open up your terminal?
Where do you install #tmux (host, default container, in each container)?
Remember the last time Fedora Silverblue or Toolbox/Toolbx got a new feature? Me neither. Both have "maintenance mode" vibes.
I finally took the plunge:
❱❱❱ sudo
bash: sudo: command not found
One less #suid root binary on my system! I don't need root on my laptop often anyway, mostly just for the weekly `bootc upgrade` and the occasional journal check. `run0` works just fine for that. (I do pretty much everything in #toolbx)
Now the remaining stuff in `find /usr -perm -4000` has mostly stuff that I don't really need, except `unix_chkpwd` and possibly `pkexec`. Getting closer!
https://github.com/martinpitt/workstation-bootc/commit/ce76ffc083baad7ad05b1eac471df9525bd71d9a
Lo que hago es tener una rama para el / los contenedores y dejo la rama principal para el directorio de usuario del sistema base.
He puesto un alias que me dice en qué rama estoy al abrir un terminal o entrar en el toolbox.
Como digo, no sé si hay soluciones más fáciles o mejores que no pasen por dejar de usar Toolbox para usar Distrobox.