<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>containerd Archives - SnapInCloud</title>
	<atom:link href="https://snapincloud.com/tag/containerd/feed/" rel="self" type="application/rss+xml" />
	<link>https://snapincloud.com/tag/containerd/</link>
	<description></description>
	<lastBuildDate>Wed, 22 Apr 2026 12:16:56 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Kubernetes Image Cleanup Timeout: containerd vs Kubelet Explained</title>
		<link>https://snapincloud.com/kubernetes-image-cleanup-timeout-containerd-vs-kubelet-explained/</link>
					<comments>https://snapincloud.com/kubernetes-image-cleanup-timeout-containerd-vs-kubelet-explained/#respond</comments>
		
		<dc:creator><![CDATA[Pratik Bandarkar]]></dc:creator>
		<pubDate>Wed, 22 Apr 2026 12:16:54 +0000</pubDate>
				<category><![CDATA[Kubernetes]]></category>
		<category><![CDATA[containerd]]></category>
		<category><![CDATA[k8s]]></category>
		<category><![CDATA[kubelet]]></category>
		<category><![CDATA[kubernetes]]></category>
		<guid isPermaLink="false">https://snapincloud.com/?p=2162</guid>

					<description><![CDATA[<p>There is no default time-based image cleanup timeout in containerd. Kubernetes relies on the kubelet's garbage collection mechanism, which removes unused images based on disk usage thresholds, not elapsed time. This post breaks down exactly how it works.</p>
<p>The post <a href="https://snapincloud.com/kubernetes-image-cleanup-timeout-containerd-vs-kubelet-explained/">Kubernetes Image Cleanup Timeout: containerd vs Kubelet Explained</a> appeared first on <a href="https://snapincloud.com">SnapInCloud</a>.</p>
]]></description>
		
					<wfw:commentRss>https://snapincloud.com/kubernetes-image-cleanup-timeout-containerd-vs-kubelet-explained/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Why Kubernetes Moved Away from Docker: The Dockershim Story</title>
		<link>https://snapincloud.com/why-kubernetes-moved-away-from-docker/</link>
		
		<dc:creator><![CDATA[Pratik Bandarkar]]></dc:creator>
		<pubDate>Fri, 22 Nov 2024 18:37:10 +0000</pubDate>
				<category><![CDATA[Kubernetes]]></category>
		<category><![CDATA[containerd]]></category>
		<category><![CDATA[docker]]></category>
		<category><![CDATA[k8s]]></category>
		<category><![CDATA[kubernetes]]></category>
		<guid isPermaLink="false">https://snapincloud.com/?p=1988</guid>

					<description><![CDATA[<p>Ever wondered why Kubernetes moved away from Docker as its container runtime? This blog explains the role of dockershim as a compatibility layer, why it was necessary, and how Kubernetes transitioned to CRI-compliant runtimes like containerd. Learn the story behind the shift and what it means for Kubernetes and Docker users today!</p>
<p>The post <a href="https://snapincloud.com/why-kubernetes-moved-away-from-docker/">Why Kubernetes Moved Away from Docker: The Dockershim Story</a> appeared first on <a href="https://snapincloud.com">SnapInCloud</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 
Content Delivery Network via N/A
Lazy Loading (feed)

Served from: snapincloud.com @ 2026-04-24 00:37:09 by W3 Total Cache
-->