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, 3:59:04 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

15 sources
> What makes a GUI app worth containerizing and CLI tools not worth containerizing? Agree 100%, and podman/docker already exist. The way I do it is to use [Distrobox](https://github.com/89luca89/distrobox) to use whatever distro's userspace has the thing I need (I use either the newer devel version of ubuntu or alpine), so if I need a newer version of a CLI tool I can get that without conflating it with the OS layer. It's a similar workflow to how OSX and Windows WSL do it. So I'm just using the normal debian packages for everything, except it's in a nice split out container just for my userspace with access to all my data. This is the workflow from Fedora Silverblue, openSUSE's MicroOS and EndlessOS, which kind of forces you into the cloud native mindset, but you can run any distro this way.
In Ubuntu 22.10 Kinetic Kudu
> I am not sure what is the story of having NixOS as a server, but would not suggest to have it as a main OS This was what I thought when I was learning nix. Once I used NixOS, I realised it's not quite that difficult. -- The two big differences: 1. Roughly, you only really need to care about the NixOS config about as frequently as you'd change system files in /etc/ in other Linux distributions. 2. Some programs (e.g. minikube) will download a binary automatically, and this doesn't work well with NixOS. I've seen tools like distrobox https://github.com/89luca89/distrobox recommended as backups on NixOS, as well as the usual Docker / VMs. I secretly suspect some of the reason NixOS is popular is it's less trouble than nix on non-NixOS. Whereas, nix on macOS, I've sometimes mixed compilers/libraries, which leads to difficult to discern prob
Read the rest
lems.
In Using Nix on macOS
Apologies, I posted this at the wrong level. I am a Manjaro user currently but have used other distros in the past, including Ubuntu. Given that, I would obviously recommend Manjaro. There are a million reasons but, for development, I find the rolling release model far superior. On Ubuntu, especially an LTS release, you are going to find over time that the software versions on your machine are too old. This will lead to installing from source or Flatpak or what have you and then your system is a mess. Worse, it also means that when you eventually move to a newer Ubuntu release, things are likely to break ( more likely at least ). Manjaro means more software updates more frequently and more hassle keeping software at older or stable versions but always up-to-date software and no big system upgrade ever again. For developers, I find the Man
Read the rest
jaro model superior. I also highly recommend looking into Distrobox. https://github.com/89luca89/distrobox Distrobox is Docker but instead of heavy sandboxing, when you are in the container you can see your real home directory, your real device tree, your real process list, and your real Wayland server ( desktop GUI ). This means you can Distrobox into an Ubuntu 20.04 LTS terminal for example and be able to run any software available Ubuntu ( including graphical ) with an experience very much like Ubuntu is installed directly on your machine. Best of both worlds. Distrobox uses Docker though so you are not going to want to run containers in Distrobox. So the real distro still matters.
In Ubuntu 22.04 LTS Released
I am a Manjaro user currently but have used other distros in the past, including Ubuntu. Given that, I would obviously recommend Manjaro. There are a million reasons but, for development, I find the rolling release model far superior. On Ubuntu, especially an LTS release, you are going to find over time that the software versions on your machine are too old. This will lead to installing from source or Flatpak or what have you and then your system is a mess. Worse, it also means that when you eventually move to a newer Ubuntu release, things are likely to break ( more likely at least ). Manjaro means more software updates more frequently and more hassle keeping software at older or stable versions but always up-to-date software and no big system upgrade ever again. For developers, I find the Manjaro model superior. I also highly recommend
Read the rest
looking into Distrobox. https://github.com/89luca89/distrobox Distrobox is Docker but instead of heavy sandboxing, when you are in the container you can see your real home directory, your real device tree, your real process list, and your real Wayland server ( desktop GUI ). This means you can Distrobox into an Ubuntu 20.04 LTS terminal for example and be able to run any software available Ubuntu ( including graphical ) with an experience very much like Ubuntu is installed directly on your machine. Best of both worlds. Distrobox uses Docker though so you are not going to want to run containers in Distrobox. So the real distro still matters.
In Ubuntu 22.04 LTS Released
distrobox to manage the container: https://github.com/89luca89/distrobox Then just install XFCE and tiger VNC server inside it. Using VNC makes it easy to connect into a little isolated session that has its own theming, etc. vs. trying to send geany to my native X11/wayland server (which wouldn't theme it like windows 95). You could also just run it in a browser window with a VNC HTML bridge, this would be a good base for that: https://github.com/accetto/ubuntu-vnc-xfce-g3 The easiest way to get Chicago95 setup is to run its GUI installer python script. I don't try to script it in a dockerfile or container setup.
In NotepadNext: A cross-platform reimplementation of Notepad++

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.