<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hcs on Luther Monson</title>
    <link>https://luth.io/tags/hcs/</link>
    <description>Recent content in Hcs on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 14 Jun 2026 20:12:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/hcs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Escaping WSL: Booting My Own Linux VM Through Hyper-V&#39;s HCS API</title>
      <link>https://luth.io/blog/2026/06/escaping-wsl-hcs-linux-vm/</link>
      <pubDate>Sun, 14 Jun 2026 20:12:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/06/escaping-wsl-hcs-linux-vm/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been building &lt;a href=&#34;https://github.com/ephpm/ephemerd&#34;&gt;ephemerd&lt;/a&gt;, a daemon that runs self-hosted GitHub Actions runners&#xA;with a fresh environment per job. On a Windows host, Windows jobs run in Hyper-V isolated containers. Linux jobs still&#xA;need a Linux kernel from somewhere. The obvious answer on Windows in 2026 is WSL2, and that&amp;rsquo;s what I used first. It worked&#xA;great from my terminal and fell over the moment ephemerd became a real Windows service.&lt;/p&gt;&#xA;&lt;h3 id=&#34;wsl2-doesnt-do-localsystem&#34;&gt;WSL2 doesn&amp;rsquo;t do LocalSystem&lt;/h3&gt;&#xA;&lt;p&gt;A Windows service that wants to create containers and Hyper-V VMs runs as &lt;code&gt;LocalSystem&lt;/code&gt;. WSL2 doesn&amp;rsquo;t support that context&#xA;at all. You get &lt;code&gt;WSL_E_LOCAL_SYSTEM_NOT_SUPPORTED&lt;/code&gt; and that&amp;rsquo;s the end of the conversation. There&amp;rsquo;s no flag for it. WSL is a&#xA;per-user feature and a service account isn&amp;rsquo;t a user.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
