<?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 Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/tags/containers/</link>
    <description>Recent content in Containers on Experiment, Fail, Learn, Repeat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 Hairizuan Noorazman</copyright>
    <lastBuildDate>Tue, 01 Sep 2026 10:36:08 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/tags/containers/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Networking Containers in Multikernel Linux Child Kernels</title>
      <link>https://www.hairizuan.com/networking-containers-in-multikernel-linux-child-kernels/</link>
      <pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/networking-containers-in-multikernel-linux-child-kernels/</guid>
      <description>&lt;p&gt;Giving a Multikernel Linux child network access is not as simple as moving the host&amp;rsquo;s network interface into it. On Google Compute Engine (GCE), the virtual NIC is also the primary kernel&amp;rsquo;s route to SSH, metadata, and the guest agent. Assigning that device or its shared controller to a child would put management access at risk.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Turning Container Images into Multikernel Linux Roots</title>
      <link>https://www.hairizuan.com/turning-container-images-into-multikernel-linux-roots/</link>
      <pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/turning-container-images-into-multikernel-linux-roots/</guid>
      <description>&lt;p&gt;My &lt;a href=&#34;https://www.hairizuan.com/can-multikernel-linux-run-on-google-compute-engine/&#34; &gt;first Multikernel Linux experiment on GCE&lt;/a&gt; started child kernels with roots that I built ahead of time. That was useful for proving that the kernels could boot, but it was not how a container runtime should consume an image. A runtime should accept the root filesystem that containerd has already prepared and should not become another registry client, layer downloader, or snapshotter.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
