<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bubblewrap on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/bubblewrap/</link>
    <description>Recent content in Bubblewrap on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/bubblewrap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Container Capabilities Management: capsh vs bubblewrap vs Native Docker Capabilities (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-22-linux-container-capabilities-management-capsh-bubblewrap-native-docker-guide/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-22-linux-container-capabilities-management-capsh-bubblewrap-native-docker-guide/</guid>
      <description>&lt;p&gt;Linux capabilities split the all-powerful root privilege into distinct units. Instead of running a container as full root (with access to every kernel operation), you can grant only the specific capabilities it needs. This guide compares three approaches to managing container capabilities: &lt;strong&gt;native Docker/Kubernetes capability controls&lt;/strong&gt;, &lt;strong&gt;capsh&lt;/strong&gt; (capability shell), and &lt;strong&gt;bubblewrap&lt;/strong&gt; (unprivileged sandbox).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
