wslc Feature Requests & Known Issues
A curated directory of 38 open wslc requests — issues and discussions from the microsoft/WSL repository (135 comments). Every item links upstream, so this page reflects the live state — nothing here is a guess.
all tracked upstream
Orchestration · SDK/API · Compatibility · Volumes · Capabilities · GPU · Networking · Registry · Platform · Hardware · Bugs · Docs
signal for what matters
Orchestration (1)
| #40948 | Compose support in wslc | 20 comments |
SDK/API (5)
| #40990 | WSL.Container API for existing containers and sessions | 9 comments |
| #41087 | Access running process in container via API | 1 comments |
| #41041 | SessionSettings name cannot contain a dot | 5 comments |
| #40991 | PortMappings in WSL.Container throws "incorrect parameter" | 6 comments |
| #41024 | WSL Container API missing features that wslc.exe already has | 1 comments |
Compatibility (4)
Volumes (1)
| #40957 | Bind-mount WSL host paths (blocks docker-in-docker) | 7 comments |
Capabilities (1)
| #41181 | Privileged container for FUSE mount | 3 comments |
GPU (2)
Networking (3)
Registry (7)
| #40945 | Pull fails behind PAC/Zscaler proxy (HTTPS_PROXY empty) | 3 comments |
| #40981 | Pull behind corporate proxy (HTTP_PROXY/HTTPS_PROXY) | 3 comments |
| #40951 | Registry mirror configuration in settings.yaml | 1 comments |
| #41030 | Credential helpers (OAuth short-lived tokens) | 3 comments |
| #41040 | Push to a different registry / repository | 3 comments |
| #41064 | Copy/retag images between registries (imagetools) | 2 comments |
| #41067 | Non-Docker-style registries (e.g. Zot) | 3 comments |
Platform (6)
| #41047 | Can wslc run on Windows Server 2022? | 1 comments |
| #41105 | Run wslc from within a WSL distro | 3 comments |
| #41029 | Persistent sysctl config (vm.max_map_count) | 1 comments |
| #40961 | vmmemwslc-cli stays running after containers exit | 3 comments |
| #41000 | Containers cannot display GUI (WSLg) | 4 comments |
| #41221 | Rollback from pre-release to stable WSL version | 0 comments |
Hardware (2)
Bugs (5)
| #41100 | wslc container cp fills RAM on large copies | 4 comments |
| #40944 | All wslc commands give E_INVALIDARG | 7 comments |
| #40987 | Home Assistant exits abnormally with -v | 5 comments |
| #40996 | wslc does not strip \r in heredoc redirection | 2 comments |
| #41222 | wslc system session terminate only supports the default session | 4 comments |
Docs (1)
| #40979 | settings.yaml broken link aka.ms/wslc-settings | 2 comments |
How we use this list
Each item here has a dedicated guide on this site where one exists. For the gaps that have a workaround, we document it; for gaps with no workaround, we say so plainly and link the issue so you can track the fix. When an issue closes, the tracker updates and the guides are revised.
Complete guide →
Start with the end-to-end overview, then drill into each tracked gap.
Compose support →
#40948 — the most-requested feature, and how to migrate today.
Docker socket & DOCKER_HOST →
#40976 — why the Engine API endpoint matters.
GPU troubleshooting →
#41050 (NVIDIA) and #40988 (AMD ROCm).
Registry & proxy →
#40945, #40981, #40951, #41030 — pull failures and mirrors.