<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on The Coders Blog</title><link>https://thecodersblog.com/tag/kubernetes/</link><description>Recent content in Kubernetes on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 08 May 2026 15:05:59 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Containers: More Than Just Linux Processes</title><link>https://thecodersblog.com/containers-beyond-linux-processes-2026/</link><pubDate>Fri, 08 May 2026 15:05:59 +0000</pubDate><guid>https://thecodersblog.com/containers-beyond-linux-processes-2026/</guid><description>&lt;h2 id="the-illusion-of-linux-centricity-unpacking-the-ocis-grand-vision"&gt;The Illusion of Linux-Centricity: Unpacking the OCI&amp;rsquo;s Grand Vision&lt;/h2&gt;
&lt;p&gt;For years, the term &amp;ldquo;container&amp;rdquo; has been almost synonymous with &amp;ldquo;isolated Linux process.&amp;rdquo; This mental model, while convenient and historically accurate, is increasingly becoming a bottleneck to understanding the full potential and reality of modern containerization. The Open Container Initiative (OCI) Runtime Specification, the very bedrock of container interoperability, was designed with a far grander, more inclusive vision. It defines containers not as mere process wrappers, but as universally applicable, isolated, and restricted execution environments. This isn&amp;rsquo;t just academic; it&amp;rsquo;s a fundamental shift enabling containerization across diverse operating systems and even, surprisingly, within virtual machines. It&amp;rsquo;s time to shed the Linux-only dogma and embrace the broader, more powerful definition.&lt;/p&gt;</description></item></channel></rss>