Migrating from Proxmox to NixOS and Incus
3 hours ago
- #Infrastructure as Code
- #NixOS
- #Agentic AI
- The author migrated from Proxmox to NixOS with Incus, citing the benefits of declarative configuration over imperative GUI-based management.
- Initial skepticism towards NixOS turned to belief after solving NVIDIA driver issues and experiencing reproducible system setups.
- Proxmox's GUI-first approach leads to state drift and difficulties with automation, especially for AI agents that need text-based systems.
- NixOS allows full control over the host, enabling features like running Kodi directly while hosting containers with Incus, avoiding trade-offs.
- Declarative text files in NixOS facilitate agentic workflows, where AI agents can read, understand, and modify infrastructure reliably.
- Incus complements NixOS by managing persistent containers and VMs, supporting legacy workloads and providing a CLI-friendly interface.
- Migration involved using tools like vzdump and qemu-img to transfer LXC containers and VMs from Proxmox to NixOS with custom scripts.
- The result is a unified, reproducible infrastructure managed from a single git repository, enhancing reliability and agentic management capabilities.