<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gitlab-Runner on Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/tags/gitlab-runner/</link>
    <description>Recent content in Gitlab-Runner 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:18:41 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/tags/gitlab-runner/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>
    
    <item>
      <title>A macOS GitLab Runner Pool with Orchard and Tart VMs</title>
      <link>https://www.hairizuan.com/a-macos-gitlab-runner-pool-with-orchard-and-tart-vms/</link>
      <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/a-macos-gitlab-runner-pool-with-orchard-and-tart-vms/</guid>
      <description>&lt;p&gt;The previous post was about Windows jobs on throw-away VMs. macOS is the same wish with harder constraints:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;macOS may only legally run on Apple hardware, so you cannot just launch a VM from a cloud image on any host.&lt;/li&gt;&#xA;&lt;li&gt;On AWS, that hardware is an &lt;strong&gt;EC2 Mac&lt;/strong&gt;, which is a dedicated host. You pay for the host, not for the instance, and a host cannot be released before 24 hours after it was allocated.&lt;/li&gt;&#xA;&lt;li&gt;A shell executor on a Mac is the easy approach, and it is how most people start. Every job then runs as the same user, in the same filesystem, with the same keychain. State leaks between jobs, and so do secrets.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The setup in this post gets one clean VM per job on a small number of Macs, without giving up much of the simplicity.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>A Fresh Windows VM for Every Job: GitLab Runner with the Fleeting AWS Plugin</title>
      <link>https://www.hairizuan.com/a-fresh-windows-vm-for-every-job-gitlab-runner-with-the-fleeting-aws-plugin/</link>
      <pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/a-fresh-windows-vm-for-every-job-gitlab-runner-with-the-fleeting-aws-plugin/</guid>
      <description>&lt;p&gt;Most of my GitLab Runner experience is Linux containers on Kubernetes (see the &lt;a href=&#34;https://www.hairizuan.com/gke-as-gitlab-runner/&#34; &gt;GKE as Gitlab Runner&lt;/a&gt; post). Windows jobs are a different story, and the first thing to learn is that &amp;ldquo;Windows runner&amp;rdquo; can mean two quite different things:&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
