In our last article we talked about Moving an install WSL Distro from it awful install folder to another drive and path. So let’s make a back up of that distro, and then install it on a different PC.
Using our new favorite tool LxRunOffline let’s make back up of a distro on our PC.
However, as one starts down the path of using LxRunOffline, there is a slight issue when it comes to WSL2 Distros:
lxrunoffline export -n openSUSE-Leap-15-1 -f suse.tar.gz
[ERROR] The action/argument “export” doesn’t support WSL2.
Ok, not a huge problem… this article just got longer…. LxRunOffline export will work for WSL 1 type Distros… So let’s do an example of both using LxRunOffline and WSL utilities.
For WSL 1 type Distros:
LxRunOffline has a command called List- from a Powershell window my list looks like this
LxRunOffline.exe list fedoraremix docker-desktop Debian Ubuntu-18.04 Ubuntu openSUSE-Leap-15-1 docker-desktop-data WLinux Ubuntu-20.04 kali-linux
Now the LX tool has a command to do a backup. This collects the distro into a Linux tar file (in Linux terms a compressed tape file).
LxRunOffline export –n <NameOfDistro> –f <pathAndNameOfExportFile>
That’s the general format of the export.
Now before one goes about exported a Distro – I would really do a WSL –shutdown Why? I think it’s best not to have any Distro’s running when you are trying to export them. It’s not a 100% required, but it is a good practice.
For WSL 2 type Distros:
Still do the WSL –shutdown.
Now we use the WSL command to backup the Distro. Like the LX tool, WSL has basically the same set of commands.
Get a list of Distros with:
wsl --list Windows Subsystem for Linux Distributions: Ubuntu-20.04 (Default) fedoraremix docker-desktop Debian Ubuntu-18.04 Ubuntu openSUSE-Leap-15-1 docker-desktop-data WLinux kali-linux
And the backup command for WSL:
wsl --export WLinux .\PengWin.tar.gz dir Directory: D:\cse.Linux Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 10/17/2020 12:46 PM 9039769600 PengWin.tar.gz
Now we have in either case a copy of our Distro that can be imported on another PC with WSL.
When using WSL.exe
WSL --import <Distro> <InstallLocation> <FileName> [Options] Imports the specified tar file as a new distribution. The filename can be - for standard input. Options: --version <Version> Specifies the version to use for the new distribution.
The –import command Allows one to name the Distro, install to a location, from a filename. The options here, –version allows one to change the WSL version while it’s being imported.
Now LXRunOffline is a little different:
lxrunoffline install Options: -n arg Name of the distribution -d arg The directory to install the distribution into. -f arg The tar file containing the root filesystem of the distribution to be installed. If a file of the same name with a .xml extension exists and "-c" isn't specified, that file will be imported as a config file. -r arg The directory in the tar file to extract. This argument is optional. -c arg The config file to use. This argument is optional. -v arg (=2) The version of filesystem to use, latest available one if not specified. -s Create a shortcut for this distribution on Desktop.
As we see the install command has a few more options beyond Name, Directory, and tar filename.
Prev Article: Moving your installed WSL Linux Distro
Why start this series with moving Distro’s around and not just about installing? Simple, The distro’s tend to default their install on the C: drive in the login user App Data space (don’t even get me started on over loading c:\users\<YourUserName>).
So what’s the problem with c:\users\<YourUserName>\AppData\Local? where do I begin… protected? hidden? Filling up your c: drive… pick one. But the most annoying one when it comes to Windows WSL distros… the install places these in the package folder. So c:\users\<YourUserName>\AppData\Local\Packages, and it does it in a way that usually involves a GUID like naming… Get the picture?
Ok, enough harping on it… Let’s get to moving things about.
You start with getting the most handy little utility called LxRunOffline. You can go to their GitHub page:
Lots of mucking about with install verbiage (that’s a bit on the side of… yeah you really don’t need to do all of that on windows 10). Just go to the release page and download the zip file already:
Unzip to a favorite directory… one that is in your execute path works fine. This gives one a exe that will execute from either a command window or powershell.
So let’s step through it…
First go ahead and install one or more of your favorite distros for WSL.
Next we move it….
## ## We will do this in Powershell ## ## Start with choosing a place we want our distro's to live... in my case the root distro I do is D:\cseWSL\<distroName> ## ## Find your user ## D:\>whoami ## I get something like mysystem\scott ## Next for the location you wish to move the distro to... i.e. in my case d:\cseWSL\Ubuntu18 ## I'm doing my Ubuntu 18.04 ## We set some access control to that directory icacls d:\cseWSL\Ubuntu18 /grant "scott:(OI)(CI)(F)" ## Here we are setting some inheriate properties and full file access to my user ## you can lookup icacls and what those parameters are from the internet ## Finding out what the distro names are ## LxRunOffline list Ubuntu ##This is same as the WSL -l command ## You can list the current location of a distro using LxRunOffline get-dir -n Ubuntu ## The -n <distro Name> is required for the get-dir command ## For my Fedora distro I get something like this .... \AppData\Local\Packages\WhitewaterFoundryLtd.Co.FedoraRemixforWSL_kd1vv0z0vy70w\LocalState ## Now the magic part... Moving a distro LxRunOffline move -n Ubuntu -d d:\cseWSL\Ubuntu18 ## the -n and -d are required for the move command ## if the named distro exists and the directory exists, then this will move the distro over ## ## To check that everything is ok with the move ## Do another LxRunOffline get-dir -n ## and see the new location ## ## Then of course, run your distro to make sure it starts up ## LxRunOffline provides a run command LxRunOffline run -n Ubuntu ## Or start the moved distro in the normal way
Seems a little much to do… but not really. It comes down to Create a Directory destination, set some permissions, and then run a command.
There we are… distros located in a Happy Place.
Ok it’s time to start a series on WSL.
I make no apologies when I say I’m not huge Linux fan, but I’m also not lacking when it comes to understanding how to utilize this OS in my Microsoft world.
First off, I’m not a newbie when it comes to matters of Linux or Unix- I spent a number of years working on HP UX with Window-X/Motif apps I had to support (so to all the Linux Trolls… yeah whatever).
So why is a “Microsoft Heavy” a.k.a. Me, ScottGeek bothering with the Linux side? Simple, over the past few years with MS moving to an inclusive approach with it’s Development tooling for cross OS apps, why wouldn’t I add Linux to my stack? Now don’t get me wrong, I’m not about to start writing code in Java or some other fork of the C language beyond C#. But Linux as a OS to deploy apps on, Linux as an IOT host, Linux as an place to share my API’s that the non-MS folks want to use- yeah that works.
So shall we begin with some topics on WSL: