Repository navigation
Releases
v0.3.0 — feat: add container restart and user-defined networks
What's Changed
- feat: add container restart and user-defined networks by @pengweiqhca in #6
Full Changelog: v0.2.0...v0.3.0
v0.2.0 — pin the WSLC session so elevation
What's Changed
- feat: pin the WSLC session so elevation does not split state by @pengweiqhca in #4
Full Changelog: v0.1.1...v0.2.0
v0.1.1 — support Testcontainers ryuk without privileged
What's Changed
- Support DOCKER_HOST translation for Docker-socket mounts via Hyper-V TCP listener by @pengweiqhca in #3
Full Changelog: v0.1.0...v0.1.1
v0.1.0 — first preview
First preview of wslc-docker-socket, a Docker Remote API surface backed by Microsoft WSL Containers (WSLC, 2.9.11 is verified). It lets Docker clients manage Linux containers on Windows without a Docker daemon.
Install
Download the archive for your architecture, extract, and run WslcDockerSocket.exe.
Requires Windows with a working WSLC runtime (wslc on PATH) and the ASP.NET Core 10 runtime or newer.
It listens on \\.\pipe\docker_engine by default — Docker's conventional pipe — so most clients need no DOCKER_HOST.
Works
- Container lifecycle: create, start, stop, wait, delete, list, inspect, logs, exec
- Archive upload (
PUT /containers/{id}/archive), streamed to WSLC without host-side extraction - Images: list with exact sizes and timestamps, inspect, anonymous pull
- Container listings report published ports and the bridge IP
- Ephemeral published ports get a real free host port allocated
- Volumes and networks: read-only list and inspect
- Verified against Testcontainers .NET with Redis, Kafka, and RocketMQ
Not supported
These return 501 with the reason rather than pretending to work, because WSLC exposes no equivalent: event streaming, TTY containers and TTY resize, image history, container attach, bind/volume/tmpfs/socket mounts, network mutation and non-default network modes, and registry credentials (anonymous pulls are accepted).
Notes
WSLC and this adapter are experimental, and the adapter performs no authentication — anyone who can reach the pipe or the optional loopback TCP port has full control over WSLC containers. Intended for local development.