Three weekends of trying to merge a NixOS machine and a Garuda box taught me a useful lesson: dual-booting means I never actually used one of them, carving a subvolume inside an existing partition took a full weekend and three recoveries, and the third attempt landed somewhere between the two and quietly failed on every reboot. So when the maintainer community behind Garuda shipped a single ISO that closes the loop without any of that work, I paid attention. The download is the same size as any other Linux ISO, the installer is the same graphical flow as any other graphical installer, and the result is a system that runs NixOS under the hood with all the Garuda defaults already wired up. That is a genuinely new thing, and it is worth a closer look from anyone who has been waiting for an excuse to try declarative Linux without a weekend of setup.
The flagship edition and a calmer alternative both shipped, both target KDE Plasma, and both share the same installer. The interesting part is what the maintainer community automated behind the scenes, because that automation is the reason this download exists at all.
Three Things I Want, and the Box That Finally Has All Three
I want atomic rollback because I have broken a system with one bad update and I do not want to do that again. I want a curated desktop because stock Arch on day one is a project, not a desktop. I want a binary cache because I do not have the patience to compile a desktop environment from source after a fresh install. The new ISO delivers all three on a single USB stick, which is unusual. Most of the time you have to pick two of three and live with the missing one.
Under the hood, the maintainer community ported their existing opinionated defaults from shell scripts and symlinks to native configuration modules, and wired a binary cache (a server that ships prebuilt packages so you do not have to compile them yourself) into the install. That last point matters because compiling everything from source is one of the reasons people bounce off NixOS in the first hour.
- Graphical installer keeps the learning curve shallow.
- Opinionated defaults ship as native configuration modules, not shell scripts.
- Prebuilt binary cache ships configured, so packages download as binaries.
- A starter config file lives at
/etc/nixosafter install. - Desktop base is recent enough for new hardware without the bleeding-edge pain.
Two Skins, One Installer, No Surprises
You only get two choices right now, and both ship with KDE Plasma. The flagship is a dark, dragon-everywhere look that the Garuda community is known for. The alternative is a lighter, calmer edition with the same underlying base. The graphical installer asks you to pick one, then offers optional extras for gaming and printer handling. That is the whole questionnaire.
What the installer actually does is more interesting than the choice of desktop. It sets up the binary cache, ports the Garuda module set to NixOS, writes the starter config, and leaves you with a bootable system on first restart. The hidden work, the subvolume plan and the rollback wiring, is done for you.
- Flagship is a dark KDE Plasma theme with full Garuda branding.
- Alternative is a calmer KDE Plasma with the same base.
- Installer handles both, with optional gaming and printer toggles.
- Installer writes a starter config at
/etc/nixos.
Rolling the Root Without Writing a Subvolume
If you have ever tried to set up the kind of root-fresh-on-boot behavior that NixOS power users love, you already know the cost. You need a subvolume layout, a list of paths to persist, a configuration that ties the two together, and enough testing to trust it. The CLI tool shipped with this edition automates that whole pipeline.
The feature itself is straightforward. Every reboot, your root filesystem rolls back to a clean snapshot, or it boots straight from a memory-backed virtual filesystem on top of an EXT4 partition. Your user account survives. Your Wi-Fi password survives. Anything outside the persisted list gets wiped unless you declared it in the configuration first.
The audit trail matters here. If something goes wrong after a reboot, you can roll back through Btrfs snapshots or simply wait for the next clean boot to clear the issue. The combination of declarative configuration and ephemeral state is what makes NixOS systems trustworthy for long-lived installations, and the new ISO gets you that behavior without the usual setup work.
- Btrfs snapshot rollback for systems that want explicit checkpoints.
- Memory-backed virtual filesystem root for EXT4 installs that want a wiped root each boot.
- Extra CLI flags beyond the simple graphical flow.
- Pre-release stability, so keep a backup machine handy.
Drawbacks Worth Naming
There are three honest costs to this approach. First, both editions are explicitly pre-release. The maintainer community labeled them as such, and that label means “do not put this on hardware that matters.” A spare laptop, a virtual machine, a test bench: those are the right hosts. Your daily driver is not.
Second, the graphical flow hides the deeper knobs. The CLI tool is where the real configuration work happens, and the maintainer community has not bridged that gap yet. Anyone who wants the full picture will end up reading the same NixOS manual they would have read on a plain install, just with a friendlier on-ramp in front of it.
Third, the cross-section of two communities creates a support seam. Most issues land cleanly in one community or the other, but a stubborn minority lands in the middle, and the middle is thin. If you are new to both NixOS and Garuda, expect to spend more time debugging than you would on a single-distro install. If you already know one, you will be fine. Plan on reading the release notes carefully before you start.
First-Run Checklist
A few practical steps if you decide to try it on hardware you can afford to wipe: download the flagship or alternative ISO from the official Garuda site, verify the checksum before flashing, and flash to a USB stick. Boot the stick on a spare machine or in a virtual machine rather than your daily driver. Run the graphical installer end-to-end, then open a terminal and try the CLI tool to see the rollback flow in action. Read the release notes before you start. They list the known quirks, and skipping them is the kind of decision you regret an hour later. Save the rollback snapshot, even on a test box, because the habit matters more than the safety on this particular install. After the install completes, take a moment to read what the CLI tool actually did to your disk, because the layout will matter if you ever need to roll back manually.
Garuda Nix is not going to replace your daily driver tomorrow, and it is not trying to. It is the friendliest on-ramp to declarative Linux that the Garuda community has ever shipped, and the rollback automation alone is worth the download. Try it on hardware you can afford to wipe, and you will learn more about how declarative systems work in an afternoon than you would in a week of reading wiki pages.