Most of the coverage around the Garuda Nix release has been about new users, the graphical installer, and the friendlier on-ramp. That angle is correct, but it leaves out a quieter story. If you already run NixOS and you want a Garuda-flavored install without re-doing your whole setup, the published flake (a reproducible Nix configuration that pins the exact source tree, inputs, and outputs) lets you do it in a single command. The same system that ships as a graphical ISO is also a nix run line away, and that is the more interesting path for anyone who has spent the last year or two rebuilding NixOS the hard way.
I have been quietly running NixOS on a couple of boxes and watching the maintainer community merge their subsystem into a real distribution. The new release is the first time I would actually recommend it to a friend who already speaks the language. The clean-boot behavior is the headline, and the existing-NixOS-user path is the quiet win that almost nobody is talking about.
The Same System, Two Different Doors
The maintainer community shipped the same distribution through two doors. The graphical ISO is the friendly path: flash a USB stick, run a graphical installer, and you land on a desktop. The flake path is the engineering path: a single nix run line pulls the installer, runs it against your chosen disk, and leaves you with the same system, configured in the same way, but without the click-through step.
Both doors land on the same machine. The graphical ISO is for people who do not yet have a system. The flake is for people who already have one and want to wipe it cleanly into this distribution. Most existing NixOS users will want the flake. Most new users will want the ISO. The maintainer community did the work to make both paths converge on the same installed system.
- Graphical ISO ships with a friendly installer, no terminal required.
- Flake path runs the same installer from a single command line.
- Both paths produce identical installed systems with the same defaults.
- Existing NixOS users should reach for the flake, not the ISO.
Two Skins, No Surprises
You will pick between Dr460nized and Mokka whichever door you use. Dr460nized is the dark, dragon-everything flagship theme. Mokka is the calmer, lighter edition with the same base. The graphical installer asks you to pick one, then offers optional extras for gaming and printer handling. On the flake path, the same choice appears as a preset in the install tool.
What the installer sets up is more interesting than the choice of desktop. It lays down a Btrfs subvolume plan, wires up the clean-boot defaults, ports the Garuda module set to NixOS, and writes the starter config to /etc/nixos. The hidden work is the subvolume plan, the persistence list, and the rollback wiring, and that work is what makes the system trustworthy on day one.
- Dr460nized is the dark KDE Plasma theme with full Garuda branding.
- Mokka is the calmer KDE Plasma with the same base.
- The installer writes a starter config at
/etc/nixos. - The hidden subvolume plan and persistence list are done for you.
Why Clean-Boot by Default Is the Real Headliner
If you have ever tried to set up the kind of root-fresh-on-boot behavior that 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 installer automates that whole pipeline, and the result is a system that boots into a clean state every time.
The audit trail is what makes this trustworthy. 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. Your per-user config folders survive. Anything else gets wiped unless you declared it in the configuration first.
The security posture is tighter than you might expect. The password hashes survive rollbacks, which means rebooting does not lock you out. Wi-Fi credentials are preserved by default. Anything outside that short list must be declared in the configuration, in text, before it persists. The system cannot slowly rot because the system cannot write to the right places by default.
- Btrfs snapshot rollback is the default behavior.
- Memory-backed virtual filesystem root is the alternative for EXT4 installs.
- Password hashes keep you logged in across rollbacks.
- Wi-Fi credentials and per-user config survive by default.
The CLI Installer Has Real Depth
If you script fleets of machines or rebuild your own setup repeatedly, the CLI installer is the part that actually matters. The install-garuda-nix tool ships with form-factor presets for desktop, laptop, server, and handheld hardware. It also exposes multiple partition layouts that combine EXT4 and Btrfs in both encrypted and unencrypted modes.
Most people will not need this. The people who do already know what they want and want it without twelve clicks. The CLI is also where you customize the persistence list beyond the defaults, set up encrypted swap, or pin package versions for a reproducible fleet. If you have ever hand-wired an impermanence-style configuration, you already know how much work this saves.
- Presets cover desktop, laptop, server, and handheld form factors.
- Partition layouts combine EXT4 and Btrfs with encryption options.
- The CLI is where deeper configuration happens.
- Scriptable for fleet provisioning or repeated rebuilds.
The Honest Trade-offs
There are three costs worth naming. First, both editions are explicitly pre-release, and the maintainer community labeled them as such. 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, if you treat system directories like a junk drawer, files there will be erased on the next reboot. The clean-boot behavior is opt-out, technically, but the entire point of this distribution is that it is on. If you turn it off, you have a regular distro with extra steps.
- Both editions are pre-release, do not use on production hardware.
- The graphical flow hides deeper knobs, the CLI is the real path.
- Clean-boot behavior is on by default, anything not declared will be wiped.
What I Would Tell Past Me
If I could send a message back to the version of me that spent a year hand-wiring impermanence-style configurations, I would say three things.
- Pull the flake, not the ISO. The single command install is faster and reproducible.
- Read the persistence list before you boot. Knowing what survives is half the job.
- Save the rollback snapshot before you start tinkering. The habit matters more than the safety on this particular install.
If you already run NixOS, the flake path is the lowest-cost way to try a Garuda-flavored install. The clean-boot default is the headline, and the existing-user path is the quiet win that almost nobody is talking about.