<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on No Semicolons</title><link>https://nosemicolons.com/tags/docker/</link><description>Recent content in Docker on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 25 Aug 2026 08:32:00 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Docker Crisis: How Generated Containerization Is Breaking Production Deployments</title><link>https://nosemicolons.com/posts/ai-generated-docker-containers-breaking-production/</link><pubDate>Tue, 25 Aug 2026 08:32:00 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-generated-docker-containers-breaking-production/</guid><description>&lt;p>Picture this: you&amp;rsquo;ve just shipped your latest feature using an AI-generated Dockerfile that looked absolutely perfect in development. Clean, concise, and it passed all your local tests. Then 3 AM rolls around, and your phone starts buzzing with production alerts. Sound familiar?&lt;/p>
&lt;p>I&amp;rsquo;ve been there more times than I&amp;rsquo;d like to admit. The rise of AI code generation has been incredible for developer productivity, but there&amp;rsquo;s a dirty secret we need to talk about: AI-generated Docker configurations are quietly breaking production deployments across the industry.&lt;/p></description></item></channel></rss>