<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Qemu on Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/tags/qemu/</link>
    <description>Recent content in Qemu on Experiment, Fail, Learn, Repeat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 Hairizuan Noorazman</copyright>
    <lastBuildDate>Sun, 22 Nov 2026 21:14:09 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/tags/qemu/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Docker-in-Docker on GitLab Runners Without Privileged: Trying Kata Containers</title>
      <link>https://www.hairizuan.com/docker-in-docker-on-gitlab-runners-without-privileged-trying-kata-containers/</link>
      <pubDate>Thu, 05 Nov 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/docker-in-docker-on-gitlab-runners-without-privileged-trying-kata-containers/</guid>
      <description>&lt;p&gt;Anyone who runs GitLab Runner on Kubernetes eventually meets this problem. A project wants &lt;code&gt;docker build&lt;/code&gt; in its pipeline. The usual answer is Docker-in-Docker (&lt;code&gt;docker:dind&lt;/code&gt;), and DinD wants &lt;code&gt;privileged: true&lt;/code&gt;. A privileged container can load kernel modules, mount host devices and, on most setups, trivially become root on the node. Every job from every project that can reach that runner then has that power.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
