<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Oci on Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/tags/oci/</link>
    <description>Recent content in Oci on Experiment, Fail, Learn, Repeat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 Hairizuan Noorazman</copyright>
    <lastBuildDate>Fri, 11 Sep 2026 17:03:51 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/tags/oci/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Running OCI Processes Inside a Multikernel Linux Child</title>
      <link>https://www.hairizuan.com/running-oci-processes-inside-a-multikernel-linux-child/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/running-oci-processes-inside-a-multikernel-linux-child/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;https://www.hairizuan.com/turning-container-images-into-multikernel-linux-roots/&#34; &gt;Turning Container Images into Multikernel Linux Roots&lt;/a&gt;, I described how an unpacked image becomes a private root for a child kernel. That gets the files into the right place, but files are not yet a running container. Something inside the child still has to interpret the OCI process configuration, establish its safety boundaries, start the executable, and translate later &lt;code&gt;exec&lt;/code&gt;, signal, terminal, and wait requests.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
