<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Podman on Subhash Dasyam</title><link>https://subhash.net/tags/podman/</link><description>Recent content in Podman on Subhash Dasyam</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 21 May 2025 22:23:13 +0400</lastBuildDate><atom:link href="https://subhash.net/tags/podman/index.xml" rel="self" type="application/rss+xml"/><item><title>Container Runtime Architecture: The Engine Room of DigiLand - PART 3</title><link>https://subhash.net/posts/container-runtime-architecture-engine/</link><pubDate>Wed, 21 May 2025 22:16:00 +0400</pubDate><guid>https://subhash.net/posts/container-runtime-architecture-engine/</guid><description>&lt;p>Before starting this please cover PART 2&lt;/p>
&lt;p>A week after their deep dive into Linux fundamentals, Maya found Connie in DigiLand&amp;rsquo;s operations center, carefully examining logs from their container platform.&lt;/p>
&lt;p>&amp;ldquo;The containers are running much better since we optimized our resource limits,&amp;rdquo; Maya observed. &amp;ldquo;But I&amp;rsquo;ve been wondering about something. When I run docker run, what exactly happens between hitting Enter and seeing the container start? What are these &amp;lsquo;runtimes&amp;rsquo; you mentioned, and what&amp;rsquo;s the difference between Docker, containerd, and runc?&amp;rdquo;&lt;/p></description></item></channel></rss>