<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rootless on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/rootless/</link>
    <description>Recent content in Rootless on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 24 Oct 2026 10:12:15 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/rootless/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Stop Docker‑Compatible Containers from Writing Sensitive Files to the Host with Rootless Mode</title>
      <link>https://linuxeries.org/post/2026-10-24-how-to-stop-dockercompatible-containers-from-/</link>
      <pubDate>Sat, 24 Oct 2026 10:12:15 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-10-24-how-to-stop-dockercompatible-containers-from-/</guid>
      <description>&lt;h2 id=&#34;why-rootless-containers-still-need-guardrails&#34;&gt;Why Rootless Containers Still Need Guardrails&lt;/h2&gt;&#xA;&lt;p&gt;Running containers as a non‑root user is a solid first line of defense, but it’s not a silver bullet. A mis‑configured image, a vulnerable app, or a simple oversight can still let a container touch &lt;code&gt;/etc&lt;/code&gt;, &lt;code&gt;/var&lt;/code&gt;, or even your own home directory. This post walks through the hardening steps that keep file writes strictly inside a rootless runtime’s writable layer.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h3 id=&#34;1-the-rootless-model-in-2026&#34;&gt;1. The Rootless Model in 2026&lt;/h3&gt;&#xA;&lt;p&gt;Rootless mode is all about user namespaces. The container’s root (&lt;code&gt;uid 0&lt;/code&gt;) gets mapped to a non‑root UID on the host, and the kernel enforces that the process can only see files that belong to that UID. The catch is that the mapping is &lt;em&gt;per‑process&lt;/em&gt;, not per‑filesystem. If a container mounts a host directory or a volume, the process inside can write to it unless the mount options explicitly deny it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
