<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Containerization on Linux Café</title>
    <link>https://mrtomlinux.org/tags/containerization/</link>
    <description>Recent content in Containerization on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 06 May 2026 10:55:11 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/containerization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Containerization Security with SELinux and AppArmor</title>
      <link>https://mrtomlinux.org/post/2026-05-06-containerization-security-with-seli/</link>
      <pubDate>Wed, 06 May 2026 10:55:11 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-06-containerization-security-with-seli/</guid>
      <description>&lt;h1 id=&#34;containerization-security-with-selinux-and-apparmor&#34;&gt;Containerization Security with SELinux and AppArmor&lt;/h1&gt;&#xA;&lt;p&gt;As we continue to navigate the complex landscape of containerization security in 2026, it&amp;rsquo;s essential to reflect on the lessons learned from the previous year. In 2025, the security community witnessed a significant increase in container-related vulnerabilities, with many of them exploiting weaknesses in container runtimes and kernel components. One notable example is the vulnerability &lt;a href=&#34;https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1271&#34;&gt;CVE-2022-1271&lt;/a&gt;, which affected the Linux kernel and highlighted the importance of robust security mechanisms.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
