How do you install any distro's packages with Distrobox?
Distrobox runs other distributions inside Podman or Docker containers, so you can install packages your own distro does not ship.
Short answer
Install Podman (or Docker), then install distrobox from your distribution's repository. Create a container with distrobox create --name box --image fedora:latest, enter it with distrobox enter box, and install whatever you need using that distro's own package manager (dnf, apt, pacman). Graphical apps you install can be exported so they appear in your host system's application menu.
What you need
Step by step
Install the container engine
Distrobox uses Podman or Docker under the hood. Podman is the recommended choice because it runs rootless: use sudo apt install podman on Ubuntu/Debian, sudo dnf install podman on Fedora, or sudo pacman -S podman on Arch. If you prefer Docker, add your user to the docker group and log out and back in.
Install Distrobox
Most distributions package it already: sudo apt install distrobox or sudo dnf install distrobox. If your repository does not carry it, use the official installer: curl -s https://raw.githubusercontent.com/89luca89/distrobox/main/install | sudo sh. Confirm the result with distrobox version.
Create the box
Pick the image of whichever distribution ships the package you want. For example, distrobox create --name fedora-box --image fedora:latest, or --image archlinux:latest for something in the Arch repositories. The first run downloads the image, so it can take a few minutes. Use distrobox list to see the boxes you have created.
Enter the box and install the package
Run distrobox enter fedora-box to step inside the container. From there you work as if you were on that distribution: sudo dnf install package_name, or sudo pacman -S package_name in an Arch box. Your home directory is mounted at the same path inside the container, so your files are right where you expect them.
Export the app to the host
Inside the container, run distrobox-export --app package_name. The application then shows up in your host's application menu and launches like any native program. For command line tools, use distrobox-export --bin /usr/bin/tool --export-path ~/.local/bin instead.
Learn cleanup and management
Type exit to leave a box. Use distrobox stop fedora-box to shut one down and distrobox rm fedora-box to delete it completely. Deleting a box removes every package you installed inside it, but the files in your home directory stay untouched.
Make the setup reproducible
For a box you use often, add a definition to ~/.config/distrobox/distrobox.ini and recreate it anywhere with distrobox assemble create. That way you do not have to retype the same setup commands each time you move to a new machine.
Tips
Watch out
Distrobox containers are not a security sandbox. Because your home directory is mounted inside the container, a malicious script run in a box can read or delete your files. Do not install images or packages from sources you do not trust.
Frequently asked questions
+Does Distrobox work like a virtual machine?
No. A virtual machine boots its own kernel, while Distrobox starts containers that share your host kernel. That means almost no performance overhead and startup in a couple of seconds.
+Will the apps I install show up in my menu?
Only if you run distrobox-export --app package_name inside the container. Without that command you can still launch the app, but only from a terminal after entering the box.
+How much disk space does it use?
Each image typically takes between 300 MB and 1.5 GB, plus whatever packages you install on top. Delete boxes you no longer use with distrobox rm to reclaim the space.
+Does it help on locked-down systems like Steam Deck or Fedora Silverblue?
Yes, that is where it shines. You can use any package manager you like inside a box without touching the immutable host system files.
+Will my files inside the box be deleted?
Your home directory lives on the host, so those files survive. Only the packages and settings installed inside the container itself are removed.
Sources and verification
Last verified: 12 Eylül 2026. tell us. Written in English; all command names and file paths are kept verbatim.
This content is for information only; for official procedures the relevant institution’s current announcements take precedence. Details: disclaimer.