<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Kaniko - Tag - vo.rs</title><link>https://vo.rs/tags/kaniko/</link><description>Kaniko - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 21 Nov 2024 14:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/kaniko/" rel="self" type="application/rss+xml"/><item><title>Kaniko: Building Container Images Inside Kubernetes</title><link>https://vo.rs/story/kaniko-building-container-images-inside-kubernetes/</link><description>&lt;p&gt;There is an awkward chicken-and-egg problem at the heart of running CI inside Kubernetes: you want to build container images, but the traditional way to build a container image is to run &lt;code&gt;docker build&lt;/code&gt;, and &lt;code&gt;docker build&lt;/code&gt; needs a Docker daemon, and a Docker daemon needs root and a bunch of kernel features that you really, really should not be handing to a CI pod. The old hack — mounting the host&amp;rsquo;s Docker socket into the build pod — is the security equivalent of leaving your front door open because the lock is fiddly. Anything that can talk to that socket effectively owns the node.&lt;/p&gt;</description><pubDate>Thu, 21 Nov 2024 14:00:00 +0000</pubDate></item></channel></rss>