<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Container on Melchi</title><link>https://melchi.me/categories/container/</link><description>Recent content in Container on Melchi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 25 May 2026 23:00:00 +1000</lastBuildDate><atom:link href="https://melchi.me/categories/container/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing your CaaS using Google's gVisor</title><link>https://melchi.me/posts/containers/</link><pubDate>Tue, 29 May 2018 10:49:15 +1000</pubDate><guid>https://melchi.me/posts/containers/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; — A standard Linux container is an isolation boundary, not a security boundary. Every container on a host shares one kernel, so a single kernel exploit can compromise the whole node. gVisor inserts a user-space kernel (&lt;code&gt;runsc&lt;/code&gt;) between your container and the host, dramatically shrinking the attack surface. It&amp;rsquo;s now production-grade — Google runs Cloud Run, App Engine and Cloud Functions on it — and integrates cleanly with &lt;code&gt;containerd&lt;/code&gt; and Kubernetes via &lt;code&gt;RuntimeClass&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>