<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cgroups on *scratch*</title>
    <link>https://www.scrivano.org/tags/cgroups/</link>
    <description>Recent content in Cgroups 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/cgroups/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why do I have two /sys/fs/cgroup in my container</title>
      <link>https://www.scrivano.org/posts/2024-1-26-why-do-i-have-two-cgroup/</link>
      <pubDate>Fri, 26 Jan 2024 14:12:00 +0200</pubDate>
      <guid>https://www.scrivano.org/posts/2024-1-26-why-do-i-have-two-cgroup/</guid>
      <description>&lt;p&gt;It happened a few times in the past that users wonder why they see two &lt;code&gt;/sys/fs/cgroup&lt;/code&gt; mounts in their unprivileged container. When working with unprivileged containers in Podman, users often notice two &lt;code&gt;/sys/fs/cgroup&lt;/code&gt; mounts if the container is not using a new network namespace. The duplication is not a bug but an intentional consequence of how the kernel handles bind mounts that cross user namespace boundaries, combined with the need to provide the container with a writable cgroup view that is scoped to its own slice.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
