<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>tempus.build blog</title><description>Engineering notes on tempus.build: runners, isolation, supply chain, and the economics of CI.</description><link>https://tempus.build/</link><language>en</language><atom:link href="https://tempus.build/en/blog/rss.xml" rel="self" type="application/rss+xml"/><item><title>Kata Containers 4.0: the runtime rewritten in Rust — what changes inside</title><link>https://tempus.build/en/blog/kata-containers-4-runtime-rs/</link><guid isPermaLink="true">https://tempus.build/en/blog/kata-containers-4-runtime-rs/</guid><description>In 4.0 the default Kata runtime becomes runtime-rs, in Rust instead of Go. What changes inside: how runtime-rs is built, what memory safety buys a host-side runtime, the new block storage model, and a verified rootfs via dm-verity/EROFS.</description><pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Kata Containers: how every CI job gets its own kernel</title><link>https://tempus.build/en/blog/kata-containers-isolation/</link><guid isPermaLink="true">https://tempus.build/en/blog/kata-containers-isolation/</guid><description>Ordinary containers share the host kernel. Kata Containers runs each pod in a lightweight VM with its own guest kernel — OCI-compatible, under containerd. A look at the Kata 3.x architecture and why it&apos;s the right boundary for untrusted CI code.</description><pubDate>Mon, 27 Jul 2026 00:00:00 GMT</pubDate></item></channel></rss>