<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Containers on </title>
    <link>https://peng.fyi/tags/containers/</link>
    <description>Recent content in Containers on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>map[name:Peng Zhang]</managingEditor>
    <webMaster>map[name:Peng Zhang]</webMaster>
    <copyright>Peng Zhang</copyright>
    <lastBuildDate>Thu, 11 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://peng.fyi/tags/containers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When enforcing OCI image spec broke customer containers</title>
      <link>https://peng.fyi/post/when-enforcing-image-spec-broke-customer-containers/</link>
      <pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate>
      <author>map[name:Peng Zhang]</author>
      <guid>https://peng.fyi/post/when-enforcing-image-spec-broke-customer-containers/</guid>
      <description>
        
          
            A container platform shipped a change to detect CPU architecture mismatches at image pull time. If an image&#39;s config says arm64 but the host is amd64, fail fast instead of letting the container start and die with exec format error. The implementation is correct, tests passed and reviewers approved.
However, it caused a production impact and a quick rollback. It turns out customers had been running mislabeled images for years. The existing code is permissive: it uses the architecture in image manifest (single-arch) or manifest index (multi-arch) as a hint to pull the image.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
