<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dev Containers on Stefan Maron | Business Central &amp; AL Development</title><link>https://stefanmaron.com/tags/dev-containers/</link><description>Recent content in Dev Containers on Stefan Maron | Business Central &amp; AL Development</description><generator>Hugo -- gohugo.io</generator><language/><lastBuildDate>Mon, 16 Mar 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://stefanmaron.com/tags/dev-containers/index.xml" rel="self" type="application/rss+xml"/><item><title>Swappable Claude Profiles: Per-Project Configs via Container Mounting (Part 3)</title><link>https://stefanmaron.com/posts/swappable-claude-profiles-container-mounting-part-3/</link><pubDate>Mon, 16 Mar 2026 09:00:00 +0100</pubDate><guid>https://stefanmaron.com/posts/swappable-claude-profiles-container-mounting-part-3/</guid><description>After Part 2 we had a working standalone container — no VS Code required, no IPC socket surprises. But there was still one problem: a single global ~/.claude folder shared across everything. One set of instructions, one list of skills, one set of agents — regardless of whether you&amp;rsquo;re doing AL development, debugging telemetry, or investigating something completely different.
That doesn&amp;rsquo;t scale. So this part introduces profile folders.
You can watch the full stream on YouTube if you want to follow along.</description></item><item><title>Claude Code in a Standalone Docker Container: Building a Real Sandbox (Part 2)</title><link>https://stefanmaron.com/posts/claude-code-standalone-docker-sandbox/</link><pubDate>Wed, 04 Mar 2026 17:00:00 +0100</pubDate><guid>https://stefanmaron.com/posts/claude-code-standalone-docker-sandbox/</guid><description>If you watched Part 1 , you know the setup: I wanted to run Claude Code in bypass-permissions (cruise mode) without worrying about it going rogue on my host. The dev container approach worked, but someone on LinkedIn pointed out that even after my VS Code IPC mitigations, Claude Code could still reconstruct the IPC bridge and escape. So Part 1 was technically broken.
Part 2 fixes that. You can watch the full stream on YouTube if you want to follow along.</description></item><item><title>AL on Linux, Dev Containers, and Codespaces</title><link>https://stefanmaron.com/posts/al-on-linux-devcontainers-codespaces/</link><pubDate>Wed, 28 Jun 2023 09:00:00 +0100</pubDate><guid>https://stefanmaron.com/posts/al-on-linux-devcontainers-codespaces/</guid><description>At BC TechDays 2023 in Antwerp, Tobias Fenster and I did a joint session called &amp;ldquo;Experiments for BC — Wasm? Codespaces? Linux? Wtf!&amp;rdquo; The full session is on YouTube if you want to watch it.
Tobias kicked things off with a deep dive into WebAssembly — what it is, where it came from, and why it might matter for the BC ecosystem. If you&amp;rsquo;re curious about running .NET or AL-adjacent code in a WASM runtime, his half is worth watching.</description></item></channel></rss>