<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Namespaces on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/namespaces/</link>
    <description>Recent content in Namespaces on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/namespaces/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Rootless Container Infrastructure: RootlessKit vs fuse-overlayfs vs slirp4netns</title>
      <link>https://www.pistack.xyz/posts/2026-05-10-rootless-container-infrastructure-rootlesskit-fuse-overlayfs-slirp4netns-guide/</link>
      <pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-10-rootless-container-infrastructure-rootlesskit-fuse-overlayfs-slirp4netns-guide/</guid>
      <description>&lt;p&gt;Running containers as the root user has long been a security concern in self-hosted infrastructure. When a container process runs as root on the host, a container escape vulnerability can grant full system-level access. Rootless container technology eliminates this risk by allowing containers to run entirely under an unprivileged user account, without requiring root privileges or setuid binaries.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
