<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Containerd on History</title><link>https://kukie.tech/tags/containerd/</link><description>Recent content in Containerd on History</description><generator>Hugo</generator><language>ko-kr</language><lastBuildDate>Wed, 21 Oct 2026 09:00:00 +0900</lastBuildDate><atom:link href="https://kukie.tech/tags/containerd/index.xml" rel="self" type="application/rss+xml"/><item><title>Network &amp; K8s.03-1 A Process in a Room</title><link>https://kukie.tech/posts/network-k8s-03-1/</link><pubDate>Wed, 21 Oct 2026 09:00:00 +0900</pubDate><guid>https://kukie.tech/posts/network-k8s-03-1/</guid><description>What a container actually is on an Ubuntu VM — three problems that VMs and containers each solve, the runtime stack from dockerd and kubelet down to runC, why runC vanishes and containerd-shim stays as the parent, the six namespaces and one cgroup directory seen through /proc.</description></item><item><title>CRI / containerd</title><link>https://kukie.tech/wiki/cri/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kukie.tech/wiki/cri/</guid><description>kubelet 과 컨테이너 런타임 사이의 규격(CRI)과, 그 규격을 구현한 대표 런타임(containerd). 실제 컨테이너는 그 아래 runc 가 만든다.</description></item></channel></rss>