I will simply list a couple of the images^[1]^ I've used over time and provide some personal insights (in alphabetical order):
- Alpine; when I'm restricted in bandwidth and/or disk space. FWIW,
apk
is even faster than whatever is found on Arch. - Arch; if I just need a certain package and can't be bothered to look up if it's available on any of the others. Yup, the AUR strikes yet again. Furthermore, if I'm troubleshooting and I find myself on the ArchWiki, then in order to prevent edge cases from happening and thus the provided solutions to not work on the non-Arch distrobox; I rely on the Arch distrobox. It doesn't hurt that
pacman
(or any of the AUR helpers) are blazing fast. However, if I intend to rely on said AUR packages over longer periods of time, then I often do look for an alternative distrobox to grab the package from instead. While the AUR is excellent for the amount of packages it has, the security standards aren't the best. Thus, if you're security-conscious, then it's better to rely on AUR packages sparingly, unless you're willing to get into the nitty gritty and check how they're built, how the package is maintained and if its maintainer(s) is reliable. - Bazzite-Arch; my go-to for gaming.
- Fedora; as I'm already on Fedora Atomic, relying on Fedora distroboxes makes the most sense security-wise. Fedora is also known to take security very seriously themselves, so in general this is just very pleasant to rely on for security reasons. The only reason why one should not rely on Fedora for security reasons would be if they're already on something from openSUSE (like Aeon/Kalpa/Tumbleweed etc). In that case, going for an openSUSE distrobox makes more sense for security. Furthermore, if the package I need is one that's widely accessible, then I also rely on Fedora distroboxes. Lastly, currently, my development environments are all Fedora distroboxes. I might eventually change these to Wolfi distroboxes or simply rely on Nix, but that's still WIP for me.
- Ubuntu; I've had to rely on these a couple of times to use software that's known to target Ubuntu. Most recently it was with Matlab IIRC.
- Wolfi; For the security-conscious, this is probably the best choice. Unfortunately, I've only experimented with it so far without too much success. Thankfully, the Bluefin project has made some good use out of it. So I'll try to emulate their ways in the near future.
Notable mention goes out to Davincibox. Unfortunately my laptop doesn't have a dedicated GPU, so I can't make use of it. But it's something I'm keeping my eyes on.
NixOS is not a supported container distro, but I do have Nix installed through The Determinate Nix Installer. It's somewhat underutilized currently, though 😅.
- The images will be the toolbox ones if available.
It seems as if the uBlue images ship the required OpenRazer kmod by default. Therefore, I would suggest you to take a look at those. You still need to follow some additional steps though 😅. Which might not be very intuitive... Thus, I propose the following: if you'll rebase to uBlue, you might as well rebase to Bazzite. After the rebase has been completed, the (post-)installation software should already give you the option (it's just a simple toggle) to install OpenRazer. The toggle is clearly visible in this frame.
If you perceive Bazzite as too opinionated for your taste, then perhaps you might opt to the following instead:
Which should be the just-entry (and thus responsible) for whatever happens after the toggle is enabled*.