@petsoi@discuss.tchncs.de in case anyone else wonders what Toolbox is:
Toolbox is a tool for Linux, which allows the use of interactive command line environments for development and troubleshooting the host operating system, without having to install software on the host. It is built on top of Podman and other standard container technologies from OCI.
Toolbox environments have seamless access to the user’s home directory, the Wayland and X11 sockets, networking (including Avahi), removable devices (like USB sticks), systemd journal, SSH agent, D-Bus, ulimits, /dev and the udev database, etc…
This is particularly useful on OSTree based operating systems like Fedora CoreOS and Silverblue. The intention of these systems is to discourage installation of software on the host, and instead install software as (or in) containers — they mostly don’t even have package managers like DNF or YUM. This makes it difficult to set up a development environment or troubleshoot the operating system in the usual way.
Toolbx solves this problem by providing a fully mutable container within which one can install their favourite development and troubleshooting tools, editors and SDKs. For example, it’s possible to do yum install ansible without affecting the base operating system.
Any advantages over distrobox? Sounds very similar.
Toolbox is more stable, but distrobox has more features
I’d use toolbx for server and distrobox for desktop.
Toolbx and Distrobox are basically identical.
The only difference is Distrobox is more agnostic and will create .desktop files for containers and applications installed in them automatically. Toolbx you need to make the .desktop manually.
deleted by creator
