You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues
Once completed please upload the output files to this GitHub issue.
If you choose to email these logs instead of attaching them to the bug, please send them to [email protected] with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
This is a real gap that blocks docker info-based tooling from treating wslc as a drop-in. Beyond the internal tool you mention, docker info is the standard first probe most Docker-ecosystem tools and scripts run to detect a working engine — Testcontainers, health-check scripts, CI preflight checks. Without wslc system info, those all fail at the first step.
The closest wslc 2.9.4.0 has is wslc version (gives the CLI + WSL versions) and wslc system session (session management). Neither exposes the engine/OS/driver summary docker info prints, so any automation that parses that shape breaks.
It's the same "drop-in replacement" gap as DOCKER_HOST (#40976) and docker context — wslc implements the container verbs but not the system-inspection surface. A wslc system info emitting a docker info-compatible JSON schema would unblock a lot of migration tooling in one shot.
Activity
github-actions commentedon Aug 7, 2026
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use
.\collect-wsl-logs.ps1 -LogProfile networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce completed please upload the output files to this GitHub issue.
See Collect WSL logs (recommended method).
If you choose to email these logs instead of attaching them to the bug, please send them to [email protected] with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
paulmartrencharpro commentedon Aug 7, 2026
Logs (in french):
Compared to docker desktop:
paulmartrencharpro commentedon Aug 7, 2026
/feature
github-actions commentedon Aug 7, 2026
Diagnostic information
ylwl1997 commentedon Aug 10, 2026
This is a real gap that blocks
docker info-based tooling from treating wslc as a drop-in. Beyond the internal tool you mention,docker infois the standard first probe most Docker-ecosystem tools and scripts run to detect a working engine — Testcontainers, health-check scripts, CI preflight checks. Withoutwslc system info, those all fail at the first step.The closest wslc 2.9.4.0 has is
wslc version(gives the CLI + WSL versions) andwslc system session(session management). Neither exposes the engine/OS/driver summarydocker infoprints, so any automation that parses that shape breaks.It's the same "drop-in replacement" gap as DOCKER_HOST (#40976) and
docker context— wslc implements the container verbs but not the system-inspection surface. Awslc system infoemitting adocker info-compatible JSON schema would unblock a lot of migration tooling in one shot.(I track which Docker-verb gaps block real tooling at https://wslcontainers.com/requirements/ —
system infois on the list.)dkbennett commentedon Oct 9, 2026
This was closed by #41408