<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nixos on Nick DeTello - Nicholas DeTello</title><link>https://nick.detello.com/tags/nixos/</link><description>Recent content in Nixos on Nick DeTello - Nicholas DeTello</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 28 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nick.detello.com/tags/nixos/index.xml" rel="self" type="application/rss+xml"/><item><title>Sharing a host's Nix store with a builder VM</title><link>https://nick.detello.com/blog/sharing-host-nix-store-builder-vm/</link><pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate><guid>https://nick.detello.com/blog/sharing-host-nix-store-builder-vm/</guid><description>A build VM can read its host&amp;rsquo;s Nix store through a read-only share. The host&amp;rsquo;s files stay immutable; the VM&amp;rsquo;s view of them doesn&amp;rsquo;t. Its garbage collector can hide shared files behind overlay whiteouts unless the VM is told, on every start, that those files are still needed.</description></item><item><title>Isolating a Nix remote builder in a microVM on a shared host</title><link>https://nick.detello.com/blog/isolating-nix-remote-builder-microvm-shared-host/</link><pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate><guid>https://nick.detello.com/blog/isolating-nix-remote-builder-microvm-shared-host/</guid><description>Distributed builds lend spare capacity to CI, but build scripts execute untrusted code. I isolate them in a builder VM with its own kernel, restricted access and resources the host can reclaim.</description></item></channel></rss>