HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
89luca89
distrobox
Go2021–2026
89luca89 / distrobox

distrobox

Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox

34Distinct people
48Mentions
0Explicit recommenders
13.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year48 dated mentions

Observed mentions: 2021-12-30 11:18:25 UTC to 2026-07-27 22:42:27 UTC.

0510152021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 15 mentions; 3 submissions, 12 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 16 mentions; 3 submissions, 13 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC110
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC15312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC16313
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC808
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC413

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Distrobox previous logo credits j4ckr3d current logo credits David Lapshin Use any Linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Distrobox uses podman, docker or lilipod to create containers using the Linux distribution of your choice. The created container will be tightly integrated with the host, allowing sharing of the HOME directory of the user, external storage, external USB devices and graphical apps (X11/Wayland), and audio. Documentation - Matrix Room - Telegram Group WarningDocumentation on GitHub strictly refers to the code in the main branch. For the official documentation Head over https://distrobox.it Distrobox What it does See it in action Why? Aims Security implications Quick Start Assemble Distrobox Configure Distrobox Installation Building from source Dependencies Install Podman without root Compatibility Supported container managers Host Distros Install on the Steamdeck Containers Distros Usage Outside the distrobox distrobox-assemble distrobox-create distrobox-enter distrobox-ephemeral distrobox-generate-entry distrobox-list distrobox-rm distrobox-stop distrobox-upgrade Inside the distrobox distrobox-export distrobox-host-exec distrobox-init Configure distrobox Useful tips Launch a distrobox from your applications list Create a distrobox with a custom HOME directory Mount additional volumes in a distrobox Use a different shell than the host Run the container with real root Run Debian/Ubuntu container behind proxy Using a command other than sudo to run a rootful container Duplicate an existing distrobox Export to the host Execute commands on the host Resolve "Error cannot open display: :0" Enable SSH X-Forwarding when SSH-ing in a distrobox Using init system inside a distrobox Using Docker inside a Distrobox Using Podman inside a Distrobox Using LXC inside a Distrobox Using Waydroid inside a Distrobox Manual Installation Automated Installation Using host's Podman or Docker inside a Distrobox Using distrobox as main cli Using a different architecture Using the GPU inside the container Using nvidia-container-toolkit Slow creation on podman and image size getting bigger with distrobox create Container save and restore Check used resources Pre-installing additional package repositories Apply resource limitation on the fly Posts Announcing the next generation of Distrobox Distrobox Next architecture Create a dedicated distrobox container Execute a command on the Host Install Podman in HOME Install Lilipod in HOME Install on Steamdeck Integrate VSCode and Distrobox Run Libvirt using distrobox Run latest GNOME and KDE Plasma using distrobox Featured Articles Articles Run Distrobox on Fedora Linux - Fedora Magazine DistroBox – Run Any Linux Distribution Inside Linux Terminal - TecMint Distrobox: Try Multiple Linux Distributions via the Terminal - It's FOSS Distrobox - How to quickly deploy a Linux distribution with GUI applications via a container Using Distrobox To Augment The Package Selection On Clear Linux - Phoronix Benchmark: benefits of Clear Linux containers (distrobox) - Phoronix Distrobox - A great item in the Linux toolbelt - phmurphy's blog Distrobox: Run (pretty much) any Linux distro under almost any other - TheRegister Day-to-day differences between Fedora Silverblue and Ubuntu - castrojo's blog Distrobox is Awesome - Running Window Manager and Desktop environments using Distrobox Japanese input on Clear Linux with Mozc via Ubuntu container with Distrobox MID (MaXX Interactive Desktop) on Clear Linux via Ubuntu container with Distrobox Running Other Linux Distros with Distrobox on Fedora Linux - bandithijo's blog Talks and Videos Linux App Summit 2022 - Distrobox: Run Any App On Any Distro - BoF Opensource Summit 2022 - Distrobox: Run Any App On Any Distro A "Box" Full of Tools and Distros - Dario Faggioli @ OpenSUSE Conference 2022 Podman Community Meeting October 4, 2022 Distrobox opens the Steam Deck to a whole new world (GUIDE) - GamingOnLinux CERN - Containerization as a means of extending the lifetime of HDL development tools How to Code with Distrobox on the Steam Deck Why you should be running the MicroOS Desktop Podcasts What it does Simply put it's a fancy wrapper around podman, docker, or lilipod to create and start containers which are highly integrated with the hosts. The distrobox environment is based on an OCI image. This image is used to create a container that seamlessly integrates with the rest of the operating system by providing access to the user's home directory, the Wayland and X11 sockets, networking, removable devices (like USB sticks), systemd journal, SSH agent, D-Bus, ulimits, /dev and the udev database, etc... It implements the same concepts introduced by https://github.com/containers/toolbox, keeping integration and broad host compatibility as primary goals. All the props go to them as they had the great idea to implement this stuff. distrobox is shipped as a single binary providing the following subcommands: distrobox assemble – create and destroy containers based on a config file distrobox create – create a container distrobox enter – enter a container distrobox ephemeral – create a temporary container, destroy it when exiting the shell distrobox list (alias: ls) – list containers created with distrobox distrobox rm – delete a container created with distrobox distrobox stop – stop a running container created with distrobox distrobox upgrade – upgrade one or more containers created with distrobox at once distrobox generate-entry – create an entry of a created container in the applications list Plus three helpers that run inside the container: distrobox-init – container entrypoint (not meant to be invoked manually) distrobox-export – export apps and services from the container to the host distrobox-host-exec – run commands/programs from t
Read the full README on GitHub

What Hacker News says

16 sources
raspberrypi.com/documentation/computers/linux_kernel.html#cross-compiling-the-kernel: https://www.raspberrypi.com/documentation/computers/linux_ke... 89luca89/distrobox: https://github.com/89luca89/distrobox #quick-start 89luca89/distrobox/blob/main/docs/useful_tips.md#using-a-different-architecture: https://github.com/89luca89/distrobox/blob/main/docs/useful_... lukechilds/dockerpi: https://github.com/lukechilds/dockerpi : RPi 1, (2,3,) in QEMU emulating ARM64 on x86_64 E.g. the Fedora Silverblue rpm-ostree distro has "toolbox" by default because most everything should be in a container containers/toolbox: https://github.com/containers/toolbox From https://containertoolbx.org/distros/ : > Distro support: By default, Toolbx creates the container using an OCI image called `<ID>-toolbox:<VERSION-ID>`, where <ID> and <VERSION-ID> are take
Read the rest
n from the host’s `/usr/lib/os-release`. For example, the default image on a Fedora 36 host would be `fedora-toolbox:36`. > This default can be overridden by the `--image` option in `toolbox create`, but operating system distributors should provide an adequately configured default image to ensure a smooth user experience. The compiler arch flags might should be correctly specified in a "toolbox" container used for cross-compilation, too. There are default gcc and/or clang compiler flags in distros' default build tools; e.g. `make` specifies additional default compiler flags (that e.g. cmake, ninja, gn, or bazel/buck/pants may not also specify for you).
In Clang now makes binaries an original Pi B+ can't run
I've been using Linuxbrew for few months last year, it was always hit-or-miss whether some tool will work or if it will be macOS only recipe. Then I started using aarch64 CPUs, and Linuxbrew still doesn't work on those. Bummer. So while I'd love to see a package manager that spans all Linux distros, Homebrew is not it, at least for now. Nix may be it, but it has its own interesting issues at times. I recently used distrobox to run Arch Linux container on Fedora host and it was a good experience. I did not try exposing the CLIs from there to the host OS but it sounds possible https://github.com/89luca89/distrobox/blob/main/docs/usage/d... . I don't want to daily-drive Arch again, but it's a great project to install fresh versions of various CLI tools from.
In Hysp – An independent package manager
I use NixOS as a daily driver. (My previous Linux of choice had been Arch). I'd describe Nix as 95% wonderful, 5% hugely painful. I learned Nix by using it on macOS/Linux before trying NixOS. I was concerned that NixOS would be very difficult to use. It was easier to use NixOS than I expected; the main problems I ran into were when a tool would helpfully download some kind of binary, but since NixOS doesn't put its shared libraries where other Linuxes do, these programs wouldn't work. -- Though, for a popular-enough tool, most likely someone else already has a Nix package written that helps out. There are other "escape hatches". e.g. I think something like distrobox could be used if native-on-NixOS stuff has problems. https://github.com/89luca89/distrobox Nix can otherwise be difficult if you need to write some Nix code. There are several
Read the rest
concepts in Nix which are foreign enough to how things have been done before; e.g. when building a package, it won't have access to $HOME; but, recent language tooling will often want access to $HOME. -- If something goes wrong, you may often need a wider and deeper understanding compared to if something goes wrong on a more typical Linux distribution. For as difficult as it is, the trade-offs Nix makes are essentially "I'm going to put in a lot of effort now, so that I don't have to put in effort some time later". (This favours Nix when "effort later" is multiplied many times). Overall, as a choice for "I need this to work right now", I'd recommend against NixOS (especially for someone who doesn't know Nix).
In NixOS and Flakes Book: An unofficial book for beginners (free)
I'm running silverblue but running my containers through distrobox. Both toolbox and distrobox are running on podman under the hood, so it's the same technology as far as I understand. However, distrobox has some interesting features relevant to this idea of development isolation. One is that it has an assemble feature[1] built-in. Where you can feed it a recipe file and it will build or rebuild containers accordingly. The other is that it allows setting a custom home directory for the container, among other host/container isolating options[2]. Perfomance wise my containers take a couple MB of rams and no perceptible CPU usage when not in use. At least as far as I can tell. [1] https://github.com/89luca89/distrobox/blob/main/docs/usage/d... [2] https://github.com/89luca89/distrobox/blob/main/docs/usage/d...
In Toolship: A more secure workstation
Gentoo ebuild USE and CFLAGS flags allow the user to specify custom compilation settings as necessary for optimization on a given processor architecture like i386, i486, i586, or i686. For example, with ebuild (or dpkg-repack or rpmrebuild) a person could build the compiler packages with all of the appropriate optimization flags for the chipset on the box where the package will be installed: https://packages.gentoo.org/useflags/custom-cflags Cross-compilation is easier with clean build containers. With distrobox (and qemu, qemu-user-static, and binfmt-support) https://github.com/89luca89/distrobox/blob/main/docs/useful_... : $ uname -m x86_64 $ distrobox create -i aarch64/fedora -n fedora-arm64 $ distrobox enter fedora-arm64 user@fedora-arm64:$ uname -m aarch64
In i386 in Ubuntu won't die
Thanks for the shout out! I haven't seen people talk about some of the other features so I'll mention a few for the others: At first you do it manually like keeping an ubuntu LTS box around for when I need to do that kind of stuff. Then over time you get annoyed that you have to maintain it and while you've removed the host-maintenance from your life it does feel like you've just shifted the problem to the right and multiplied it every time you make a new box. So the next logical step is to just make it declarative, so it's one of the reasons we made boxkit. Distrobox has an exciting new feature coming out called assemble: https://github.com/89luca89/distrobox/blob/main/docs/usage/d... And since all this stuff is just docker containers you can just pick your distro, pick your list of packages, and then let git and the automation deal with
Read the rest
it, you'll always have your dev environment. Assemble was the last missing piece, I'm looking forward to duct taping all of this together! https://github.com/ublue-os/boxkit is the "kit" if anyone wants to help out, when you fork it it'll bring the github actions with it, so you can set up builds of your boxes and they'll always be up to date. It's based on alpine but that part can be swapped out no problem. And for those of you who think this is just too far, `distrobox upgrade` can be useful when you have way too many pets.
In Distrobox: Use any Linux distribution inside your terminal
I was curious about the same, so had a look round. The main innovation in blendOS is the "blend" package manager: https://github.com/blend-os/blend Under the hood, this uses "distrobox" to create containers for supported distributions: https://github.com/89luca89/distrobox Supported distributions are defined in "blend" here: https://github.com/blend-os/blend/blob/4e4bdd33d2de374cb01e4... Additionally, there are wrappers for commands like "apt", which in turn call "blend", which in turn calls "distrobox": https://github.com/blend-os/blend/blob/main/pkgmanagers/apt In contrast, Bedrock Linux has a quite different implementation, with the most widely used strategy being based on "strata" and a FUSE filesystem "crossfs". See "How does Bedrock Linux Work?" on https://bedrocklinux.org/faq.html#how-work
In New Distro 'BlendOS' Combines Arch Linux, Fedora Linux and Ubuntu

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.