<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker Engine 29.8.0 on Cloudkaramchari</title><link>https://www.cloudkaramchari.com/tags/docker-engine-29.8.0/</link><description>Recent content in Docker Engine 29.8.0 on Cloudkaramchari</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>cloudkaramchari</copyright><lastBuildDate>Sun, 13 Sep 2026 12:20:00 +0530</lastBuildDate><atom:link href="https://www.cloudkaramchari.com/tags/docker-engine-29.8.0/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Engine 29.8.0: --umask Flag, Custom AppArmor Profiles, and CloudWatch Entity Logging</title><link>https://www.cloudkaramchari.com/blog/docker-engine-29-8-0-umask-apparmor-cloudwatch-entity-logging-guide/</link><pubDate>Sun, 13 Sep 2026 12:20:00 +0530</pubDate><guid>https://www.cloudkaramchari.com/blog/docker-engine-29-8-0-umask-apparmor-cloudwatch-entity-logging-guide/</guid><description>
&lt;h1 id="docker-engine-2980---umask-flag-custom-apparmor-profiles-and-cloudwatch-entity-logging">Docker Engine 29.8.0: --umask Flag, Custom AppArmor Profiles, and CloudWatch Entity Logging&lt;/h1>
&lt;p>Docker Engine 29.8.0 shipped on September 3, 2026, and it's a release worth actually reading the changelog for instead of skimming past. It doesn't add a headline feature — it closes four small, specific gaps that practitioners have been working around with entrypoint scripts, custom AppArmor policies deployed by hand, or CloudWatch dashboards missing service context. If you run containers with strict file-permission requirements, manage your own AppArmor policy, ship logs to CloudWatch, or run anything on top of Docker's VMM/Hyper-V backend, at least one of these changes affects you directly.&lt;/p></description></item></channel></rss>