Repository navigation
wslc container rm --force fails when the container does not exist #42009
Description
Windows Version
Microsoft Windows [Version 10.0.26200.9711]
WSL Version
3.0.3.0
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
6.18.54.1-1
Distro Version
N/A (wslc container command)
Other Software
- Docker 29.9.1, build dfc520d (comparison only)
Repro Steps
- Run
wslc container rm does-not-exist --force --volumes, where no container
nameddoes-not-existexists. - Check the exit code.
Expected Behavior
--force should make a missing container a no-op, as in Docker:
> docker rm does-not-exist --force --volumes
> echo $LASTEXITCODE
0
Docker prints nothing and exits 0. That lets scripts run an idempotent
cleanup such as rm --force before run, with no existence check.
Actual Behavior
> wslc container rm does-not-exist --force --volumes
Container 'does-not-exist' not found.
Error code: WSLC_E_CONTAINER_NOT_FOUND
If this error was unexpected, please consider searching for existing issues or filing a new issue at https://github.com/microsoft/WSL/issues.
> echo $LASTEXITCODE
1
The same happens without --volumes.
wslc container rm --help describes --force as "Delete containers even if
they are running". It says nothing about missing containers.
Diagnostic Logs
N/A
Activity
github-actions commentedon Oct 21, 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'.
polys commentedon Oct 21, 2026
/feature
github-actions commentedon Oct 21, 2026
Diagnostic information
ggarzia-MSFT commentedon Oct 21, 2026
Thanks for reporting this bug, I was able to repro
polys commentedon Oct 22, 2026
Thank you!