Diagnosing Failed NixOS Configuration Switches
Learn how to diagnose and fix failed 'nixos-rebuild switch' operations, including activation failures, disk exhaustion, and how to perform atomic rollbacks.
Loading…
ReadMeFeed / Community knowledge
#nix-store
Real questions. Useful conversations. Find the people who know your stack.
nixosNixOS Architecture Note: Declarative System Design and Operational Boundaries
How to decide if NixOS fits your infrastructure, where trust boundaries sit, and how to check generations and garbage collection.
NixOS Generations: Why Your Rollback Plan Lives in the Bootloader
NixOS makes system changes atomic by storing each activation as an immutable generation. Learn how to verify a rollback target and clean up safely.
How NixOS’s Atomic Generations Make Zero‑Downtime Upgrades a Reality
Upgrade a production NixOS server safely by leveraging atomic generations. Learn the step‑by‑step process, a useful example, and the trade‑offs that come with NixOS's declarative system.
NixOS Atomic Upgrades: How Generations Enable Safe Rollbacks
NixOS builds each system version as an immutable closure in the Nix store; switching updates symlinks atomically, and the --rollback flag lets you return to a prior generation when a change fails.
Atomic Upgrades in NixOS: How System Generations Make Rollbacks a Breeze
NixOS’s system generations turn upgrades into a risk‑free experiment. Learn how atomic rollbacks, disk‑space trade‑offs, and mutable‑state limits shape a safe upgrade workflow, complete with a step‑by‑step example.
Atomic Upgrades and Safe Rollbacks in NixOS: How Generations Protect Your System
Learn how NixOS creates immutable system generations, performs atomic upgrades with `nixos-rebuild switch`, and rolls back safely—plus what to watch for when garbage collection threatens those generations.
NixOS Automatic GC and Generation Retention: Bootloader Limit Behavior Needs Diagnosis
Retention Boundaries Between Boot Menu Limits and Store Deletion NixOS derives system state from a declarative configuration and keeps prior generations in the Nix store so rollbacks remain possible. Garbage collection is not automatic unless a systemd timer or manual invocation triggers it, while the bootloader's configurationLimit controls how many generat