Skip to content
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

Enable Changing Where Subsystem Files are Stored #5044

Closed
Vandivier opened this issue Apr 4, 2020 · 2 comments
Closed

Enable Changing Where Subsystem Files are Stored #5044

Vandivier opened this issue Apr 4, 2020 · 2 comments

Comments

@Vandivier
Copy link

Is your feature request related to a problem? Please describe.
My C drive is near capacity.

When using WSL + Ubuntu, I ran Add-AppxPackage from my storage drive (D:).

I also previously configured my Windows 10 Storage settings to "Change Where New Content is Saved" including "New Apps will Save to" my storage drive, but I notice the files are put on C: anyway. I would argue this is a bug, but Stack Exchange states it's simply not supported.

Describe the solution you'd like

  1. If I run Add-AppxPackage on a remote drive, the subsystem files are stored on that drive.
  2. From inside subsystem, if I install a package it can be saved to a folder I chose, potentially on another drive.

The two above can be implemented separately. For implementation on WSL side, I think it's easier to continue WSL installation on my main drive, but when I sudo apt-get install unzip, for example, that stuff can be put on my storage drive.

@therealkenc
Copy link
Collaborator

/dupe #449. YRMV on the discussion over there; it is just the landing zone for the topic.

There is wsl.exe --import and --export on recent releases, although that isn't quite the same ask.

@ghost
Copy link

ghost commented Apr 4, 2020

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants