Skip to content

wslc: support wslc system info #41282

Closed
Closed

Description

@paulmartrencharpro

Is your feature request related to a problem? Please describe.
docker info (https://docs.docker.com/reference/cli/docker/system/info/) is used by one of my company internal tool to check the workstation installation before running it.
So, I cannot replace docker desktop with wslc for this.

Describe the solution you'd like
Implement "wslc system info" - https://docs.docker.com/reference/cli/docker/system/info/

Activity

  1. github-actions commented on Aug 7, 2026

    @github-actions
    Contributor

    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:

    Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
    Set-ExecutionPolicy Bypass -Scope Process -Force
    .\collect-wsl-logs.ps1
    

    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.

    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'.

  2. paulmartrencharpro commented on Aug 7, 2026

    @paulmartrencharpro
    Author

    Logs (in french):

    > wslc system info
    Copyright (c) Microsoft Corporation. Tous droits réservés.
    Pour plus d’informations sur la confidentialité de ce produit, veuillez consulter https://aka.ms/privacy.

    Commande non reconnue : 'info'
    Commandes de gestion de niveau système.

    Utilisation : wslc system [] []

    Les sous-commandes suivantes sont disponibles :
    session Gérer les sessions.

    Pour en savoir plus sur une commande spécifique, passez-la à l’argument aide. [-?]

    Les options suivantes sont disponibles :
    -?,--help Affiche l’aide sur la commande sélectionnée

    Compared to docker desktop:

    > docker info
    Client:
    Version: 29.6.2
    Context: desktop-linux
    Debug Mode: false
    Plugins:
    agent: Docker AI Agent Runner (Docker Inc.)
    Version: v1.115.0
    Path: C:\Users[username].docker\cli-plugins\docker-agent.exe
    ai: Docker AI Agent - Ask Gordon (Docker Inc.)
    Version: v1.27.0
    Path: C:\Users[username].docker\cli-plugins\docker-ai.exe
    buildx: Docker Buildx (Docker Inc.)
    Version: v0.35.0-desktop.2
    Path: C:\Users[username].docker\cli-plugins\docker-buildx.exe
    compose: Docker Compose (Docker Inc.)
    Version: v5.3.1
    Path: C:\Users[username].docker\cli-plugins\docker-compose.exe
    debug: Get a shell into any image or container (Docker Inc.)
    Version: 0.0.47
    Path: C:\Users[username].docker\cli-plugins\docker-debug.exe
    desktop: Docker Desktop commands (Docker Inc.)
    Version: v0.4.3
    Path: C:\Users[username].docker\cli-plugins\docker-desktop.exe
    dhi: CLI for managing Docker Hardened Images (Docker Inc.)
    Version: v0.0.7
    Path: C:\Users[username].docker\cli-plugins\docker-dhi.exe
    extension: Manages Docker extensions (Docker Inc.)
    Version: v0.2.31
    Path: C:\Users[username].docker\cli-plugins\docker-extension.exe
    init: Creates Docker-related starter files for your project (Docker Inc.)
    Version: v1.4.0
    Path: C:\Users[username].docker\cli-plugins\docker-init.exe
    mcp: Docker MCP Plugin (Docker Inc.)
    Version: v0.43.3
    Path: C:\Users[username].docker\cli-plugins\docker-mcp.exe
    model: Docker Model Runner (Docker Inc.)
    Version: v1.2.6
    Path: C:\Users[username].docker\cli-plugins\docker-model.exe
    offload: Docker Offload (Docker Inc.)
    Version: v0.6.9
    Path: C:\Users[username].docker\cli-plugins\docker-offload.exe
    pass: Docker Pass Secrets Manager Plugin (beta) (Docker Inc.)
    Version: v0.2.0
    Path: C:\Users[username].docker\cli-plugins\docker-pass.exe
    sandbox: "docker sandbox" is deprecated, use Docker Sandboxes instead (Docker Inc.)
    Version: v0.13.0
    Path: C:\Users[username].docker\cli-plugins\docker-sandbox.exe
    scout: Docker Scout (Docker Inc.)
    Version: v1.23.1
    Path: C:\Users[username].docker\cli-plugins\docker-scout.exe

    Server:
    Containers: 4
    Running: 2
    Paused: 0
    Stopped: 2
    Images: 3
    Server Version: 29.6.2
    Storage Driver: overlayfs
    driver-type: io.containerd.snapshotter.v1
    Logging Driver: json-file
    Cgroup Driver: cgroupfs
    Cgroup Version: 2
    Plugins:
    Volume: local
    Network: bridge host ipvlan macvlan null overlay
    Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
    CDI spec directories:
    /etc/cdi
    /var/run/cdi
    Discovered Devices:
    cdi: docker.com/gpu=webgpu
    Swarm: inactive
    Runtimes: nvidia runc io.containerd.runc.v2
    Default Runtime: runc
    Init Binary: docker-init
    containerd version: e53c7c1516c3b2bff98eb76f1f4117477e6f4e66
    runc version: v1.3.6-0-g491b69ba
    init version: de40ad0
    Security Options:
    seccomp
    Profile: builtin
    cgroupns
    Kernel Version: 6.18.35.2-microsoft-standard-WSL2
    Operating System: Docker Desktop
    OSType: linux
    Architecture: x86_64
    CPUs: 14
    Total Memory: [redacted]
    Name: docker-desktop
    ID: [redacted]
    Docker Root Dir: /var/lib/docker
    Debug Mode: false
    HTTP Proxy: http.docker.internal:3128
    HTTPS Proxy: http.docker.internal:3128
    No Proxy: hubproxy.docker.internal
    Labels:
    com.docker.desktop.address=npipe://\.\pipe\docker_cli
    Experimental: false
    Insecure Registries:
    hubproxy.docker.internal:5555
    ::1/128
    127.0.0.0/8
    Live Restore Enabled: false
    Firewall Backend: iptables

  3. paulmartrencharpro commented on Aug 7, 2026

    @paulmartrencharpro
    Author

    /feature

  4. github-actions commented on Aug 7, 2026

    @github-actions
    Contributor
    Diagnostic information
    Found '/feature', adding tag 'feature'
    
  5. ylwl1997 commented on Aug 10, 2026

    @ylwl1997

    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.

    (I track which Docker-verb gaps block real tooling at https://wslcontainers.com/requirements/ — system info is on the list.)

  6. dkbennett commented on Oct 9, 2026

    @dkbennett
    Member

    This was closed by #41408

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions