#toolbx now has a new security policy based on GitHub's private vulnerability reporting. This is meant to lighten the load on the larger GitHub Containers organization, on whose shoulders we were standing for the past six years. See: https://github.com/containers/toolbox/security
Build software better, together

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

GitHub
Toolbox Distros

Website illustration for containertoolbx.org demonstrating support for multiple distros running as guest.

art.jimmac.eu

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

Two new #toolbx bug-fix releases are now available to address CVE-2025-65637 or GHSA-4f99-4q7p-p3gh in Logrus that affects some long-term support distributions: https://github.com/containers/toolbox/releases
Releases · containers/toolbox

Tool for interactive command line environments on Linux - containers/toolbox

GitHub
@almostsurely #Toolbx, one per project, subdirs on homedir. Takes more disk space having one per project, but the purpose is keep separate dependencies.

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)?

...
#linux #silverblue

@passthejoe because it's the default on whatever it is you're running? I think #distrobox is probably a better option for a desktop usecase, but #toolbx is perfectly cromulent for a server, where you're basically just using #microOS or #coreOS for a container host, it doesn't need to be fancy.

Remember the last time Fedora Silverblue or Toolbox/Toolbx got a new feature? Me neither. Both have "maintenance mode" vibes.

#Fedora #Silverblue #AtomicFedora #Toolbx #Toolbox

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.

#Toolbx