WSL.Container API for existing containers

[hultqvist]

Is your feature request related to a problem? Please describe.
While testing the new SDK the program crashed.
Next time it failed to create the container because one with that name already existed.
Right now it does not appear that there is a way to manage already existing containers.

container = session.CreateContainer(containerSettings);

Describe the solution you'd like
Any of the following:

session.GetContainers();
container = session.OpenContainer(...);
new ContainerSettings
{
    ReplaceIfExist = true,
}

Describe alternatives you've considered

The alternative right now is to clear up the container using wslc.exe

RunCommand("wslc.exe", $"--session {SessionName} stop {ContainerName}");
RunCommand("wslc.exe", $"--session {SessionName} rm {ContainerName}");

Additional context
Add any other context or screenshots about the feature request here.

NuGet: Microsoft.WSL.Containers 2.9.3
wslc 2.9.3.0

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

[hultqvist]

/feature

[github-actions]

Diagnostic information

Found '/feature', adding tag 'feature'

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

[hultqvist]

/feature

[github-actions]

Diagnostic information

Found '/feature', adding tag 'feature'