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

Si necesitáis crear imágenes ISO, he encontrado una herramienta mediante línea de comandos para #Linux que parece ir bien.

Lo he probado en un contenedor de #Toolbx basado en #Fedora y me ha funcionado. https://www.wikihow.com/Create-an-ISO-File-in-Linux

How to Create an ISO File in Linux: 4 Easy Methods

Create an ISO file from files, folders, a CD, or a DVDThis wikiHow guide teaches you how to turn a group of files into an ISO file on a Linux computer. You can use the Linux command line (terminal) to do this, or try a simple free...

wikiHow
@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

¿Alguien usa toolbx / toolbox en lugar de distrobox? ¿Cómo mantenéis el directorio de usuario limpio de modificaciones y cambios en los ficheros de configuración?

Yo estoy probando esto, pero no sé si hay alguna solución mejor: https://marcel.is/managing-dotfiles-with-git-bare-repo/

#Fedora #Toolbx

Managing dotfiles with a bare git repo

I use dotfiles to configure my environment. I had the dotfiles stored in a git repo and used helper scripts to create symlinks in my `$HOME` directory. However, adding & updating the dotfiles felt cumbersome, like a pebble in a shoe.

A new #toolbx bug-fix release is now available that helps to address the CA certificates bug that broke OpenSSL recently: https://github.com/containers/toolbox/releases/tag/0.3
Release 0.3 · containers/toolbox

Security fixes Bumped the minimum github.com/go-viper/mapstructure/v2 version to 2.4.0 for GHSA-2464-8j7c-4cjm Bug fixes Deprecated all containers that need the org.freedesktop.Flatpak.SessionHe...

GitHub