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

8 sources
I strongly recommend just switching the Dev environment over to Linux and taking advantage of tools like "distrobox" and "toolbx". https://github.com/89luca89/distrobox https://containertoolbx.org/ It is sorta like Vagrant, but instead of using virtualbox virtual machines you use podman containers. This way you get to use OCI images for your "dev environment" that integrates directly into your desktop. https://podman.io/ There is some challenges related to usermode networking for non-root-managed controllers and desktop integration has some additional complications. But besides that it has almost no overhead and you can have unfettered access to things like GPUs. Also it is usually pretty easy to convert your normal docker or kubernetes containers over to something you can run on your desktop. Also it is possible to use things like Kuber
Read the rest
netes pods definitions to deploy sets of containers with podman and manage it with systemd and such things. So you can have "clouds of containers" that your dev container needs access to locally. If there is a corporate need for window-specific applications then running Windows VMs or doing remote applications over RDP is a possible work around. If everything you are targeting as a deployment is going to be Linux-everything then it doesn't make a lot of sense to jump through a bunch of hoops and cause a bunch of headaches just to avoid having it as workstation OS.
In We're Leaving Kubernetes
Developer setups are the foremost use case for toolbox (atomic Fedora) or distrobox [0]. Dev toolchains are infamous for pulling a ton of stuff into your system, and certain languages make switching versions a pain as well. So you install your IDE and whatever flavour of the month tools you need in a distrobox container, using regular dnf packages, and keep your base system clean. With distrobox you can give those tools a separate $HOME as well, in case they litter your main one with dotfiles and dotfolders. If you work on a certain project long-term, you can then clone the distrobox and keep it around as-is, to ensure against breaking changes in some of your tools. [0] https://github.com/89luca89/distrobox
In The VS Code Flatpak is useless
I'm surprised the post title says "with focus on running containers". That would be Colima, AFAIK, which uses Lima but is a separate project. See https://github.com/abiosoft/colima. Colima is meant as a free replacement for Docker Desktop on Mac OS. Lima, OTOH, is more of a nice way to run a Linux VM on Mac in a way that integrates the guest and the host systems to a good degree by default. It wraps either QEMU or Apple's VZ framework. In my mind, Lima is spiritually similar to https://github.com/89luca89/distrobox, but for a Mac host For a more traditional VM GUI, there's https://mac.getutm.app/ which is a completely separate free project that also wraps QEMU or VZ. It will run any OS you want, not just Linux.
In Linux virtual machines, with a focus on running containers
Regarding the stability issue on a dev machine - you may be interested in playing with one of the immutable-os distros, such as SilverBlue (fedora based). The high-level take-away is you can't break your actual OS since it's root filesystem is read-only, and you use "pet" containers (on docker, podman, whatever) to do your work in. Applications are either sandboxed via Flatpak, or installed/run inside your pet containers. If your pet container dies, you cry about it for a moment, and when you're ready you get a new one - your actual os and other containers remain unaffected. I use distrobox[1] to create/run the pet containers. [1] https://github.com/89luca89/distrobox
In Windows 11 now comes with its own adware
A Rockchip RK3588S with an NPU TPU and an RTC battery is a good idea for safer complex SBC applications. From https://news.ycombinator.com/item?id=38007967 : > The RTk.GPIO is a Plug & Play USB Device which adds 28 x Raspberry Pi style GPIO pins to your computer An RP2040 (RPi Pico) is also a USB 2x20 GPIO, with a uf2 bootloader and upgradeable firmware. Conda-forge builds arm64 Linux and now MacOS packages from feedstocks. There's usually not a maintained arm64 copy of containers though, so you must build containers yourself with or for ARM64 with cross-compilation from a faster build machine, which distrobox makes really simple. https://news.ycombinator.com/item?id=38505448 ... https://github.com/89luca89/distrobox/blob/main/docs/useful_...
In Raspberry Pi is manufacturing 70K Raspberry Pi 5s per week
> What does this project add? This project uses this upcoming feature in Fedora: https://fedoraproject.org/wiki/Changes/OstreeNativeContainer... and switches to its consumption model entirely. On stock Fedora you're pulling from a distribution-hosted ostree endpoint to do updates. With Bluefin (and other universal-blue.org images) you're pulling from a container registry (in this case ghcr.io, but you can push your builds to any registry or host your own). We ingest Fedora daily and then add codecs, a bunch of hardware enablement support via udev rules, add a few pain-in-the-ass-otherwise things like the obs virtual cam, xbox controller support, etc. Then that image is pushed to ghcr.io and the local package manager uses that. We also enable Flathub out of the box and Distrobox: https://github.com/89luca89/distrobox - then ship a few pre
Read the rest
configured boxes for you to play with: Ubuntu, Fedora, and Wolfi. Then we have another image that you can rebase to by typing `just devmode` in a terminal which adds vscode with devcontainers, devpod, devbox, kvm/qemu, incus/lxc/lxd, some nice monospace fonts, cockpit, kind, docker, and a bunch of associated cluster tools. And since we build everything in CI there's no local package conflicts like in upstream Fedora when the main repo and rpmfusion repos are conflicting, your PC only ever gets successfully built images.
In Project Bluefin: an immutable, developer-focused, Cloud-native Linux

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.