Unable to start containers under certain conditions

[AmelBawa-msft]

Reference: https://task.ms/61506292

Create container with --rm option

PS C:\src\wsl> wslc container create --name Demo -e 'A=B' --rm alpine:latest env
e3fe954042919aded004bf25334f8046c88a31c98d2e4b9b5ab97153217cb66d

PS C:\src\wsl> wslc start Demo -a
Element not found.
Error code: ERROR_NOT_FOUND

Starting container with attach option

PS C:\src\wsl> wslc container create --name Demo -e 'A=B' alpine:latest env
ddd34f7f0c433354d2a84045e7d144e863d6a8a7e1cd0c43599c93379e40671a

PS C:\src\wsl> wslc start Demo -a
The group or resource is not in the correct state to perform the requested operation.
Error code: ERROR_INVALID_STATE

[github-actions]

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 wsl-gh-logs@microsoft.com 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'.