WSL containers is now generally available – Windows Developer Blog

Commenters explained that the announcement is about running Linux containers on Windows via WSL, effectively launching a Linux VM that hosts containers in a Windows-native way. Several noted practical benefits for Windows-centric environments: one tester said it got them "about 90% of the way" for custom containers and liked that WSL containers behave like microVMs and are implemented as Windows services, which eases concerns among non-technical managers (davoneus). Another commenter emphasized that it’s a first‑party alternative to Docker on Windows with native terminal integration and enterprise controls - group policy, Defender instrumentation, and Defender for Endpoint hooks that make monitoring and resource restrictions manageable like any other Windows asset (OneDeuxTriSeiGo). A basic description of WSL as a Windows feature for running Linux environments was also cited (troelsSteegin).

Others pushed back on usefulness and tradeoffs. Some framed it as just another VM with attendant overhead and inefficiencies (MrDrMcCoy, cogman10), or said it’s awkward compared to running Linux natively and not attractive if you can move off Windows (VCFundedGenYer). Critics argued it enables more corporate compliance tooling and admin control - useful to BOFHs but onerous to developers (grim_io) - and one warned of Microsoft’s “extend and extinguish” behavior around platform control (davoneus). Opinion divides sharply between those who value enterprise integration and centralized management on Windows and those who prioritize lightweight, native Linux container workflows and fear lock‑in, overhead, or increased corporate control.