DOSSIER 15 / 6 ARTICLES
NixOS virtualization and deployment
From disposable VMs to images, remote nodes, and cloud resources, manage build outputs separately from runtime state.
Start with the first articleFollow the question further.
This topic covers QEMU virtual machines, custom ISOs, dockerTools container images, SSH deployment, Terraform cloud resources, and layered environment design. Understand system configuration in an isolated environment first, then choose an image or remote delivery path. At every step, distinguish evaluation, building, activation, runtime verification, and data recovery.
- 01
Use a minimal VM to observe how configuration and qcow2 state change independently, then try graphical sessions.
Validating NixOS configuration with QEMU
From a minimal configuration to GNOME and Sway, distinguish VM declarations from persistent disk state.
Read article - 02
Learn ISO modules and Flake output paths; verify the whole-disk device and backups before writing a USB drive.
Building a bootable NixOS ISO
Customize software, graphical desktops, and bootable images through installation-media modules.
Read article - 03
Understand the boundaries between application closures, image layers, running instances, and database volumes.
Building and running container images with dockerTools
Manage application derivations, runtime closures, and container data state separately.
Read article - 04
Read in the order build, test, switch, and rollback, checking SSH identity and sudo permissions.
Deploying NixOS over SSH
Distinguish local builds, temporary remote activation, persistent switching, and failure rollback.
Read article - 05
Separate cloud-resource plans and state from NixOS generations, paying special attention to AMIs, routing, and the two interpolation layers.
Dividing deployment responsibilities between Terraform and NixOS
Manage cloud resources with Terraform, then deploy NixOS system configuration through a controlled process.
Read article - 06
Choose Flatpak, Distrobox, VMs, or servers according to dependency, permission, and recovery needs rather than pursuing absolute isolation.
Designing layered desktop and development environments
Choose between the host, Flatpak, Distrobox, virtual machines, and servers based on dependency and permission boundaries.
Read article