Jan-Willem HarmannijAdded a "distrobox create" and "distrobox enter" test to the #AeonDesktop openQA tests:
https://openqa.opensuse.org/tests/5973555
This will hopefully catch any issues with #Distrobox on Aeon faster in the future.
Root MooseAnyone had success running Distrobox (Debian/Ubuntu vm) under Alpine Linux to get Blender with Cycles/HIP support working on an Alpine host? Something I gotta try...
#Linux #Alpine #AlpineLinux #Blender #ROCm #AMD #HIP #Distrobox #Podman #Docker
nfoertIโve spent some time this weekend reinstalling my desktop with #CachyOS. Previously it used #bazzite, as it was mostly used for gaming, but I was also using it to run some heavier game servers and doing all of that in #distrobox was getting annoying. So far itโs been a nice experience, and Iโm enjoying being able to mess stuff up again 
Uri Herrera 
I was checking out Kontainer (nice project, by the way) for a GUI for #Distrobox. I clicked on the About entry in the hamburger menu, and lol, I see #Nitrux is still setting trends in #KDE software, huh.
๐ช๐
๐๐๐๐ฮฉ๐๐๐๐I finally flicked the switch from #bluefin to a custom #nixos flake with #distrobox and #flatpak support in early February. Loving it. There's no going back!
The flake offers a curated basic setup that vibes well with #ublue spins. I'll release it after ironing out a few things and adding an installation ISO.
tkissingOMG how did I not know about #distrobox before? I spent 2 days researching distros and one evening trying to get Fedora and Bazzite to play nice next to each other and next to Windows, all with Secure Boot on when all I needed to fix my dev environment issues was to install vscodium and asdf inside an Arch distrobox...
Crest of LightThere is something deeply amusing about running openSUSE Tumbleweed in Distrobox and the frontend Distroshelf, and installing a program there for usage on my Arch-based distro.
It's fun and makes me quite happy, I want to eventually play more with dev stuff so this makes sense for me to do. At first in simple ways, then more complex ways! Still not ready to totally handle a pure terminal workflow, so Distroshelf is a lifesaver for me!
Larvitz 
New post: Distrobox: Different Distributions in a Box, Powered by #Podman 
The case for running Arch, Ubuntu, and a real RHEL userspace as long-lived containers on a Fedora laptop. Home directory mounted in, GUI apps integrated, VSCode treats the box as a remote target.
Bonus: on a Fedora host registered with subscription-manager, RHEL entitlements propagate into UBI containers automatically via Podman's default mounts.conf. No flags, no manual bind mounts.
Especially good on Atomic spins.
https://blog.hofstede.it/distrobox-different-distributions-in-a-box-powered-by-podman/
MuemmelOver the last months I tried to move from gui to cli. Started with shift from #kde plasma to #niri. On Ubuntu 24LTS this was quite problem, first I used #pacstall, but that was better, I changed to #nix package manager, it simply has a the packages, no need to cargo and apt/nala as much. Also I can chair stuff simpler between systems. Nix also enabled me to remove everything but one #distrobox container. As #arch already has #qgis 4
Droppiemany many many hours later...
- it turned out that, despite all appearances to the contrary, in fact #distrobox actually is [mostly] working ok in my main pooter's real โ
โ ๐ฎ
- there clearly are two bugs with it [again, only here, not in my VMs], coz as i showed before, the process of entering the container never [seems to] complete... but i discovered by accident several hours later, when, furious at this idiocy, i had begun contemplating a clean installation of โโ ! ... the new container/s do get listed in the plasma apps menu despite the apparent terminal hang ๐ฎ
- when said new DB container terminal/s are then launched, they incorrectly continue to indicate they are โโ sessions, but despite this mis-labelling, in fact it/they are the container ones, eg, in this new โ
โ sid one,
so, after unnecessary hours if not day of stress & profanities, i'm now belatedly orf to da races re my #cunningplan
- it turned out that, despite all appearances to the contrary, in fact #distrobox actually is [mostly] working ok in my main pooter's real โ
โ ๐ฎ- there clearly are two bugs with it [again, only here, not in my VMs], coz as i showed before, the process of entering the container never [seems to] complete... but i discovered by accident several hours later, when, furious at this idiocy, i had begun contemplating a clean installation of โ
โ ! ... the new container/s do get listed in the plasma apps menu despite the apparent terminal hang ๐ฎ- when said new DB container terminal/s are then launched, they incorrectly continue to indicate they are โ
โ sessions, but despite this mis-labelling, in fact it/they are the container ones, eg, in this new โโ sid one, pacman throws errors of "not installed", which is the first clue, then apt ofc does run ๐ฎso, after unnecessary hours if not day of stress & profanities, i'm now belatedly orf to da races re my #cunningplan