<?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 *scratch*</title>
    <link>https://www.scrivano.org/tags/bubblewrap/</link>
    <description>Recent content in Bubblewrap on *scratch*</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 06 Jun 2026 10:03:54 +0000</lastBuildDate>
    <atom:link href="https://www.scrivano.org/tags/bubblewrap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Use bubblewrap as an unprivileged user to run systemd images</title>
      <link>https://www.scrivano.org/2016/10/22/use-bubblewrap-unprivileged-user-run-systemd-images/</link>
      <pubDate>Sat, 22 Oct 2016 13:21:25 +0000</pubDate>
      <guid>https://www.scrivano.org/2016/10/22/use-bubblewrap-unprivileged-user-run-systemd-images/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/projectatomic/bubblewrap/&#34;&gt;bubblewrap&lt;/a&gt; is a sandboxing tool that allows unprivileged users to run containers. I was recently working on a way to allow unprivileged users to take advantage of bubblewrap to run regular system images that use systemd. To do so, it was necessary to modify bubblewrap to retain a controlled set of Linux capabilities inside the sandbox. Without those capabilities, systemd cannot perform the privilege-separation steps it needs at startup, even when running as UID 0 inside a user namespace.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
