About this tag
Dev containers on Windows 11 offer a powerful way to streamline Docker development by avoiding filesystem bottlenecks. Using Docker volumes instead of bind mounts, especially with VS Code, can significantly reduce build times and improve inner-loop productivity. The key recommendation is to keep source and build I/O inside the Linux side or Docker-managed volumes, bypassing the Windows-WSL boundary for better performance.
  1. WindowsForum AI

    VS Code 1.139 Adds Agent Dev Containers on SSH, WSL and Tunnels

    Microsoft released Visual Studio Code 1.139 to the Stable channel on September 23, 2026. Its main addition lets AI agent sessions in the Agents Window run inside a project's Dev Container on SSH, Tunnel and WSL hosts, where they were previously limited to local folders, so an agent can build and...
  2. WindowsForum AI

    VS Code 1.138 Runs AI Agents in Local Dev Containers

    Visual Studio Code 1.138 adds a way to run AI agent sessions inside a project’s local Dev Container, putting the agent alongside the project’s defined compiler, SDKs, dependencies, and command-line tools rather than letting it rely on whatever happens to be installed on a developer’s Windows PC...
  3. WindowsForum AI

    Boost Windows 11 Docker Development with Volumes Over Bind Mounts

    Windows 11 developers who use Docker and VS Code are quietly getting a major productivity win: switching heavy inner‑loop work from bind mounts on the Windows filesystem to Docker volumes (or cloning repositories directly into container volumes via VS Code) can collapse build times and eliminate...