-
Notifications
You must be signed in to change notification settings - Fork 841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL --unregister should not delete if system was imported in-place #12427
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload 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-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging |
/feature This was tagged already, this reply is really unnecessary. |
Diagnostic information
|
Is your feature request related to a problem? Please describe.
If a user uses --import-in-place, then the usage itself would be indicative of the user managing the lifetime of the root filesystem outside of WSL built-in management semantics; as such, WSL should not delete the root filesystem when doing "--unregister"
Describe the solution you'd like
One of two options:
A) Unregister should not delete user data when image was created with "import-in-place"
B) Unregister should never delete user data. There should be an --unregister and --delete command. Similar to this #9932 - but I think we should just have two options [--unregister] and [--delete]
Describe alternatives you've considered
The workaround is somewhat simple to just --terminate + copy the image somewhere else, then do unregister, but it's ugly.
The text was updated successfully, but these errors were encountered: