<?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 Aayush Bajaj's Augmenting Infrastructure</title><link>https://abaj.ai/tags/oci/</link><description>Recent content in Oci on Aayush Bajaj's Augmenting Infrastructure</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Aayush Bajaj</copyright><lastBuildDate>Thu, 09 Jul 2026 21:02:05 +1000</lastBuildDate><atom:link href="https://abaj.ai/tags/oci/index.xml" rel="self" type="application/rss+xml"/><item><title>Containers</title><link>https://abaj.ai/wiki/se/implementation/containers/</link><pubDate>Thu, 09 Jul 2026 21:02:56 +1000</pubDate><guid>https://abaj.ai/wiki/se/implementation/containers/</guid><description>&lt;p>a container is not a small virtual machine. it is an ordinary linux process (tree) that the kernel has been told to &lt;em>lie to&lt;/em> — about what processes exist, what the filesystem looks like, what the network is, who root is — plus an accountant capping what it may consume. the lying is &lt;strong>namespaces&lt;/strong>, the accounting is &lt;strong>cgroups&lt;/strong>, and everything else (images, registries, orchestrators) is packaging around those two syscall families (Tanenbaum, Andrew S., 2008).&lt;/p></description></item></channel></rss>