<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Filesystem Isolation on Nalar</title>
    <link>https://nalar.dev/tags/filesystem-isolation/</link>
    <description>Recent content in Filesystem Isolation on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/filesystem-isolation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Mount Propagation Defines the Filesystem Boundary Between Linux Mount Namespaces</title>
      <link>https://nalar.dev/mount-propagation-defines-the-filesystem-boundary-between-linux-mount-namespaces/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/mount-propagation-defines-the-filesystem-boundary-between-linux-mount-namespaces/</guid>
      <description>&lt;p&gt;A process can enter a new Linux mount namespace and still observe a later mount created elsewhere. The namespace boundary is intact: the process has its own mount table. The new mount appears because some mounts in the two namespaces remain connected by propagation relationships.&lt;/p&gt;&#xA;&lt;p&gt;This distinction matters in container runtimes, service sandboxes, build systems, and privileged helpers. Creating a mount namespace separates the namespace&amp;rsquo;s view of the mount table, but it does not by itself make every future mount event local. Shared-subtree state determines whether mount and unmount events cross that boundary.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
