<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Debian on Tony Metzidis</title>
    <link>https://tonym.us/tag/debian.html</link>
    <description>Recent content in Debian on Tony Metzidis</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 06 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://tonym.us/tag/debian/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Isolated &amp; Sandboxed WSL Environments with Debian Slim</title>
      <link>https://tonym.us/isolated-sandboxed-wsl-debian-slim.html</link>
      <pubDate>Mon, 06 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://tonym.us/isolated-sandboxed-wsl-debian-slim.html</guid>
      <description>&lt;p&gt;This approach moves away from the &amp;ldquo;one big distro&amp;rdquo; model, which often leads to&#xA;100GB+ VHDX files and dependency hell. Instead, we use a modular, immutable-ish&#xA;workflow by utilizing the &lt;code&gt;debian:stable-slim&lt;/code&gt; Docker image as our &amp;ldquo;Gold&#xA;Master.&amp;rdquo; It makes recovery loads easier, and isolates each project,&#xA;which is expecially important with so many supply chain attacks today.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-architecture-of-a-sandboxed-wsl-environment&#34;&gt;The Architecture of a Sandboxed WSL Environment&lt;/h2&gt;&#xA;&lt;p&gt;The goal is to create a clean &lt;strong&gt;Base Image&lt;/strong&gt;, snapshot it, and then spin up lightweight, project-specific &lt;strong&gt;Instances&lt;/strong&gt;. This ensures that an experimental library or a legacy Node.js version in one project never touches your primary development environment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
