<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Capabilities on Compose, Break, Repeat</title>
    <link>https://lours.me/tags/capabilities/</link>
    <description>Recent content in Capabilities on Compose, Break, Repeat</description>
    <image>
      <title>Compose, Break, Repeat</title>
      <url>https://lours.me/profile.png</url>
      <link>https://lours.me/profile.png</link>
    </image>
    <generator>Hugo -- 0.154.2</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Sep 2026 09:00:00 +0200</lastBuildDate>
    <atom:link href="https://lours.me/tags/capabilities/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker Compose Tip #89: What cap_drop actually takes away from root</title>
      <link>https://lours.me/posts/compose-tip-089-capability-dropping/</link>
      <pubDate>Wed, 23 Sep 2026 09:00:00 +0200</pubDate>
      <guid>https://lours.me/posts/compose-tip-089-capability-dropping/</guid>
      <description>cap_drop: ALL restricts root itself, not just non-root users, and the capability you&amp;#39;d reach for to prove it might already be a no-op on your host.</description>
    </item>
    <item>
      <title>Docker Compose Tip #29: Container capabilities and security options</title>
      <link>https://lours.me/posts/compose-tip-029-container-capabilities/</link>
      <pubDate>Thu, 12 Feb 2026 09:00:00 +0100</pubDate>
      <guid>https://lours.me/posts/compose-tip-029-container-capabilities/</guid>
      <description>Fine-tune container security with Linux capabilities and security options</description>
    </item>
  </channel>
</rss>
