Repository navigation
wslc inspect doesn’t accept Docker-style /name container references (breaks Dev Containers “Attach”) #41846
Description
Windows Version
Microsoft Windows [Version 10.0.26200.9457]
WSL Version
3.0.1.0
Are you using WSL 1, WSL 2, or WSLC?
- WSL 2
- WSL 1
- WSLC
Kernel Version
6.18.40.1-1
Distro Version
Red Hat Enterprise Linux release 9.8 (Plow)
Other Software
Dev Containers 0.469.0
VS Code 1.142.0-insider
Repro Steps
> wslc inspect --type container /test-wslc
Object not found: /test-wslc
[]
> wslc inspect --type container test-wslc
[ { ... } ] # worksExpected Behavior
Same result as docker inspect /test-wslc. Docker stores names with a leading / and accepts both forms.
Actual Behavior
Dev Containers → “Attach to Running Container” calls wslc inspect --type container /test-wslc and fails with “Cannot attach to the container with name/id /test-wslc, it no longer exists.”
Diagnostic Logs
No response
Reacted by z-xhh
Activity
github-actions commentedon Oct 9, 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'.
deamen commentedon Oct 9, 2026
This has been reported in the vscode-remote-release microsoft/vscode-remote-release#11841
But feels like this is a compatibility issue in wslc, as podman does not have this issue
deamen commentedon Oct 9, 2026
/emailed-logs
/emailed-logs
github-actions commentedon Oct 9, 2026
Diagnostic information