<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rootless on Thomas Van Laere</title><link>https://thomasvanlaere.com/tags/rootless/</link><description>Recent content in Rootless on Thomas Van Laere</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thomasvanlaere.com/tags/rootless/index.xml" rel="self" type="application/rss+xml"/><item><title>Exploring Containers - Part 4</title><link>https://thomasvanlaere.com/posts/2026/10/exploring-containers-part-4/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://thomasvanlaere.com/posts/2026/10/exploring-containers-part-4/</guid><description>&lt;p&gt;Six years ago, I started this series to see what was inside the container black box. &lt;a href="https://thomasvanlaere.com/posts/2020/12/exploring-containers-part-3/"&gt;Exploring Containers - Part 3&lt;/a&gt;, which closed it out in late 2020, left me with a better appreciation for what it takes to get a container up and running. Since then, I&amp;rsquo;ve often revisited those posts. I still find them useful when troubleshooting container-related issues.&lt;/p&gt;
&lt;p&gt;Even though I&amp;rsquo;d argue that, as of last year but most certainly now in 2026, it is much faster and more efficient to let an LLM drudge through the layers of CLI commands, parsing logs and looking at these kernel constructs, provided you choose a sufficiently capable model. I still find value in hands-on exploration to understand the nuances and interactions within a containerized environment. And with more teams deciding what to host themselves and what to leave to the cloud, I think it makes sense to understand containers from the ground up.&lt;/p&gt;</description></item></channel></rss>