quickemu VS distrobox

https://github.com/quickemu-project/quickemu

Tl;Dr use quickemu: https://github.com/quickemu-project/quickemu

There's also quickgui to help with launching VMs: https://github.com/quickgui/quickgui

(I've been using it for annual chores on windows)

[2] https://github.com/quickemu-project/quickemu/blob/0c8e1a5205...

Multipass is pretty clutch for trivial VMs on MacOs for sure. I use it for a bunch of ssh jump boxes running vpns to different sites. The macOS build does not support custom images (lest not without [some truly insane hacks](https://github.com/canonical/multipass/issues/1260#issuecomm...) , which doesn’t really matter for what I use it for but it is kind of a bummer. If you need something with a little more grunt but don’t want to go full blown with writing your own QEMU tooling or fussing with something like UTM or Parallels, [quickemu](https://github.com/quickemu-project/quickemu) is a really nice qemu wrapper with sane defaults that can expose a whole lot of power if you need it.

Also: https://github.com/quickemu-project/quickemu/issues/88

Overall, don't be afraid to switch distro (use Ventoy, load a few ISOs just in case), try to make sure you have an easy way of backing up your stuff (be it with a separate /home partition, or like I do with storing everything important in a separate drive and then using symlink to make it 'appear' in their 'default' places), and you can always use VM in a pinch (consult this guide or use quickemu or gnome-boxes)

In case some things you do absolutely needs Windows, keep this guide for setting up VM in mind, or use quickemu's GUI.

VM will be shutdown automatically when it's inactive for a while. I will eventually add more distros going forward. Most distro isos are downloaded using the quickget script from the wonderful quickemu project. You may directly contribute to the upstream project to get the distro added to DistroSea.

If you want to do this super easily, check out the QuickEmu project with the QuickGUI: https://github.com/quickemu-project/quickemu

Looks great! Does anyone know how Virter compare with quickemu?

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

Distrobox is a tool that enables us to try Linux distro CLI, including their package manager. This requires a containerization tool (e.g., Docker). In Windows, this can be achieved using WSL (Windows Subsystem for Linux)

I use containerized versions of things, ubuntu and chainguard images mostly.

You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_...

https://news.ycombinator.com/item?id=38505448 ... https://github.com/89luca89/distrobox/blob/main/docs/useful_...

Yes, you can do that but I've seen others use something like distrobox to run linux inside of SteamOS: https://github.com/89luca89/distrobox/blob/main/docs/posts/steamdeck_guide.md

For such cases you might use something like this: https://github.com/89luca89/distrobox

Btw #3: Depending on what the user is trying to accomplish, e.g. maybe to make WSL(2) itself more of a "subsystem" than a "container engine", using something like Distrobox or nsbox.dev can be a good idea (along with Docker or Podman in Distrobox's case; the other one uses systemd-nspawn).

1. Find here in "Containers Distros" section the distro image that you want to install ("Toolbox" versions are better because they are configured for Distrobox) and get it URL: https://distrobox.it/compatibility/#containers-distros 2. Use that URL to create Distrobox: distrobox create -i registry.fedoraproject.org/fedora-toolbox:39 -n fedora_1_39 3. Enter Distrobox fedora_1_39: distrobox enter fedora_1_39 4. You are already in Distrobox console. Look at the name in console, it should be include the container name. 5. To exit Distrobox: exit 6. If you run: distrobox list you will see all distroboxes on the system. You will also see that distrobox that we exited is still running. 7. To stop distrobox use commands: distrobox stop fedora_1_39