If you are Choosing between BoxBuddy and DistroShelf To manage Distrobox, here you'll find a straightforward comparison with real-life steps. I'll tell you what each one does, how to install them, where they shine and where they fail, and what you should keep in mind to make sure everything runs smoothly from the start.
The grace of these interfaces is bring Distrobox closer to everyday use without losing isolation and order, integrating applications from other distributions into your desktop as if they were native, but keeping your host system clean and without surprises.
What are Distrobox, BoxBuddy and DistroShelf?
Distrobox is the foundation: create containers of multiple Linux distributions integrated with your system, so you can run software from other distros without heavy virtual machines or bare-metal installations.
BoxBuddy is a graphical interface for Distrobox that simplifies common tasks, such as creating containers, entering them, updating them, or exporting applications. Important: Distrobox is not included; you must have it previously installed on your system.
DistroShelf is another graphical interface focused on managing Distrobox with a modern UI (GTK 4 and libadwaita), with features for creating and managing containers, viewing status and details, installing packages, managing exported apps, opening terminals, updating, cloning, and deleting containers. It's available in the AUR and nixpkgs-unstable, allows you to choose your preferred terminal emulator from Preferences, and is free software licensed under the GPL 3.0 or later.
Prerequisites and compatibility
Before you jump in, make sure you've got the basics covered: Distrobox installed and configured, GTK 4 and libadwaita (for DistroShelf) and a compatible terminal emulator.
Commonly supported terminal emulators: GNOME Terminal, Konsole, Xfce Terminal, Tilix, Alacritty, and more; you can set your preferred one in DistroShelf's Preferences.
Installing Distrobox and BoxBuddy (real-life example on openSUSE)
Installing Distrobox is direct from the package manager, for example with the command for openSUSE: sudo zypper install distrobox.
BoxBuddy is distributed as a Flatpak, so it is advisable to check that Flathub is configured (official guide at docs.flathub.org) and then install: flatpak install flathub io.github.dvlv.boxbuddyrs
BoxBuddy Permissions: To view and manipulate your user containers and files, adjust permissions from the desktop settings (in Plasma) or with Flatseal, granting access to your home directory.
If you are going to use Docker as a backend, add your user to the docker group and enable the service, with something like: sudo usermod -aG docker $USER, sudo systemctl start docker y sudo systemctl enable docker; then reboot for the permissions to take effect.
Although BoxBuddy is not required to use Distrobox, In practice, it makes creating, managing, and accessing containers much more convenient.
Installing and compiling DistroShelf
In Arch/derivatives you can pull from the AUR (distroshelf), And on Nix, you can use the nixpkgs-unstable package; if you're compiling from source, the classic flow would be to clone the repository and build/install with the tools listed in its README.
After installation, open DistroShelf and adjust the terminal emulator you want to use, as it supports GNOME Terminal, Konsole, Xfce Terminal, Tilix, Alacritty and others, all from its Preferences box.
Creating containers with BoxBuddy (and DistroShelf equivalents)
Creating containers in BoxBuddy is as simple as pressing the “+” button and choosing the distribution, with options like enabling an init system if you need it and deciding whether to use your default home directory or a specific one for that container.
Real example: Create a Kali Linux container to keep your security tools handy without running a VM or dedicating a machine to it. You can leave the home field empty to use your host's home address (or define an alternate one if you're looking for more separation).
DistroShelf offers a similar flow: choose distro, container name and parameters, also managing states, clones and deletion from its interface at a glance.
Enter the container: one click or terminal
From BoxBuddy you can open a terminal inside the container with a button, or do it the classic way with distrobox enter NOMBRE (for example, distrobox enter Kali).
On first access, you will be asked to define user password in the container, You'll see welcome messages or recommendations for the guest distribution; from there, you're in, operating with its native package manager.
Update containers and packages
BoxBuddy makes upgrading easy with its “Upgrade Box” option that opens a terminal and asks for your password to continue, running the process with the package manager of the container distro.
You can also update all your containers from the terminal with Distrobox utilities, following the usage documentation for upgrades and maintenance.
In the case of Kali within Distrobox, a typical flow would be to update and then install metapackages, e.g. kali-linux-default for the standard set, kali-tools-vulnerability for vulnerability assessment and kali-tools-reporting for reporting tools.
The experience is very close to being in that “real” distro, with its package manager and repositories, but with Distrobox integration that makes it feel native to your host session.
Export applications to the system menu
One of the most powerful features is exporting apps from the container to the host application menu, running them as if they were native. When the UI fails or has insufficient permissions, the terminal saves the day.
Basic export command: distrobox-export --app xhydra (replace xhydra with whatever app you want); if all goes well, Distrobox will tell you the app has been exported and will appear in your launcher in a few seconds.
To unexport (remove from the menu), add the delete option, with distrobox-export --app xhydra --delete; this is how you clean the entrance when you no longer need it.
Note about BoxBuddy: The “View Apps” view may not list apps due to permissions issues; if this happens, check Flatseal or file permissions, or use the commands above while tweaking settings.
Clone and delete containers
In DistroShelf you have a clear option to clone containers and another to delete them, ideal for testing environment variations without starting from scratch or for cleaning up what you no longer use.
In BoxBuddy, deleting a container is a couple of clicks with confirmation, and in terminal the direct order is distrobox-rm NOMBRE (for example, distrobox-rm Kali).
Remember that you can list your containers with Distrobox utilities, which also show in a very visual way which ones are running at that moment.
Comparison: BoxBuddy vs. DistroShelf
- User experience: BoxBuddy focuses on extreme simplicity for common tasks; DistroShelf, powered by GTK 4/libadwaita, adds richer status views and controls for cloning and advanced management from the UI.
- Managing exported apps: Both support this, but if BoxBuddy doesn't list apps by permission, the terminal is your ally; DistroShelf includes a panel to manage exports directly when everything is configured correctly.
- Integration with terminals: DistroShelf allows you to explicitly choose the emulator (GNOME Terminal, Konsole, Xfce Terminal, Tilix, Alacritty, and more); BoxBuddy works well with popular terminals, although it doesn't boast as much of this selection in its UI.
- Installation and availability: BoxBuddy shines for its availability on Flathub as a Flatpak (io.github.dvlv.boxbuddyrs), while DistroShelf is convenient for Arch (AUR) and Nix (nixpkgs-unstable) users, with the option to compile from source.
- Power vs. Simplicity: If you want a straightforward approach to creating, logging into, and updating containers, BoxBuddy delivers; if you’re interested in viewing statuses, cloning, and a more comprehensive dashboard from the GUI, DistroShelf may be a better fit.
Good practices and useful tips
Isolating “rare” apps in containers simplifies host updates, avoiding adding dozens of third-party repositories to your main distro and reducing time and risks with each update.
Export only what you really use, This way, you don't clutter your menu with unnecessary entries and you keep the separation between productive and experimental aspects clear.
Consider using a dedicated home per container if you need watertightness, especially if you're going to be messing around with pentesting tools or library versions that you don't want mixed up with your host user.
If you use Docker as backend, don't forget the docker group and restart, Because permissions aren't always applied just by logging out; a reboot prevents headaches later.
For lists and statuses, the Distrobox command that shows active containers is gold, Since you can see at a glance what's running and what's not, which is very useful when managing multiple environments.
Limitations and small “buts” detected
App listings in BoxBuddy that do not appear are usually a permissions issue, and are fixed by adjusting user file access or checking Flatpak permissions with Flatseal.
Bash history inside the container may not persist as you expect, which forces you to memorize commands or adjust shell settings if you want a more consistent history.
Metapackages (like in Kali) install a lot at once and sometimes it's hard to see what's in there, so it is a good idea to consult the metapackage documentation to find out exactly what tools have been added.
Recommended workflows with Kali on Distrobox
Please update first and then install the base metapackage (kali-linux-default), and then add groups like kali-tools-vulnerability o kali-tools-reporting depending on your use case.
Export to your menu only the tools that you open often, for example a scanner or a specific GUI, and leave the rest accessible from the terminal so as not to fill the launcher.
If you notice strange behavior in graphical integration, Review container environment variables and Distrobox options to improve integration with the host.
Privacy, banners and community signals
Some content on the web includes very intrusive cookie and privacy notices, typical of platforms like Reddit, which detail cookie use, ad personalization and measurement.
You'll also see threads or posts with “Like” counters and empty comment sections, Signs of interest, but not always in-depth technical content; this reinforces the value of a solid, centralized guide.
When to choose BoxBuddy or DistroShelf
- Choose BoxBuddy if you want a straightforward interface, available via Flathub and with essential tasks just a click away, perfect for creating containers, entering, updating and exporting without complications.
- Choose DistroShelf if you prefer a more complete UI where you can see status, clone and manage exports in detail, and you move well with GTK 4/libadwaita environments and ecosystems like AUR or Nix.
In both cases, Distrobox is the protagonist and the difference is in the “wrapping”, so the decision depends on your workflow and how you like to manage your environments.
Useful resources and reference links
- Distrobox Quick Start Guide: The official Quick-Start documentation explains how to create and enter containers step by step.
- Using upgrades in Distrobox: There is a specific section in the documentation for updating containers and keeping them up to date.
- BoxBuddy on Flathub and its repository: you will find the identifier io.github.dvlv.boxbuddyrs and the corresponding installation/permit instructions.
- DistroShelf in AUR and nixpkgs-unstable: Useful if you are an Arch or Nix user, with notes on dependencies (GTK 4, libadwaita) and supported terminals.
- Complementary tools: Flatseal for Flatpak permissions, package managers for each guest distro, and system utilities to enable Docker if you're using it as a backend.
- If you are looking to centralize very specific tools (such as utilities for TI calculators or similar), Consider isolating them in their own container and exporting only the executable you use, gaining cleanliness and control.
In the end, the combination of Distrobox + a good GUI multiplies the flexibility of your desktop, allowing you to test, work, and update without messing up your base distro and with everything at hand when you need it.
