Skip to main content

WSL + Interop + Azure: $HOME is everywhere

Introduction

Microsoft //BUILD is just 3 days away and while I'm just (super) sad that I will not attend, I wanted to bring a "special" gift.
After some discussion on Twitter with @Tara_msft, she asked me if I tried Azure Cloud Shell.
She past a link to the (incredibly) excellent @docmsft site. And the Pandora box was definitively open...

The crazy idea

after looking at the Cloud Shell, and reading about Spot Instant Cloud, this (crazy) idea came to life:
What if, I could tweak the "$HOME" hack and make it available "everywhere"! 
Or, due to the limitation of the Azure free account (in terms of storage capacity) and the "Network drives" permissions/behavior, at least I could put the important dot files in the Cloud Drive while keeping the development files on the "Interop zone" (read: /mnt/c/...) as described in Brian's blog post.

To be prepared, you must

Before we can apply what follows, some preparation is needed.
The major one being: you must have an Azure account. Gladly, Microsoft offers a free account!

Once you completed the creation of your new account, you can login to https://shell.azure.com/ if you want a full page console, or login to https://portal.azure.com and click on the Cloud Shell icon.
The first time, it will warn you that you need to create an Azure Files Storage.
Follow this guide to get you fully started.

 On your computer, you need to have WSL installed with your preferred distribution (search for Linux in Microsoft Store).

Mounting the Clouddrive: Windows side

Ok, first of all: we want to mount the Azure Shell Cloud drive in WSL, so what is this Windows side all about?
Well, it's simple, for mounting the Cloud Drive in Linux, we need Fuse and for the time being, it's still not handled in WSL.
However, we can mount Windows drives into WSL, and following the docs, we can mount (read: network drive) the Cloud Drive in Windows.

 Here is a quick summary based on the docs:  
  1. Connect to https://portal.azure.com
  2. Click on "Storage Accounts" on the left menu
  3. You should see at least one line with the Cloud Shell drive
  4. Click on the name to get to the account summary page
  5. Click on "Files" to get the file share details
  6. Click on the name of the file share
  7. Click on "Connect" to see the connection helper on the right
  8. Open an Explorer window and click on "This PC"
  9. Click on "Map Network drive"
  10. Choose the drive letter and enter the network path that you see in the "net use" connection helper and click on "Connect using different credentials"
  11. Click on finish
  12. Enter the username with the "Azure" domain
  13. Enter the access key as the password
  14. Click OK to complete the mapping
You should now be able to see you drive mounted with, normally, only one directory ".cloudconsole"

Mounting the Clouddrive: WSL side

As all the heavy lifting was done on Windows side, on WSL we will simply map the drive:
  1. Launch your favorite distro (here I will use Ubuntu)
  2. Mount the drive with the letter you chose (here I will use Z:) to either the "/mnt/" path or, in my case, to a directory in my $HOME
And that's all! Here is the gif I made to share on Twitter the full setup with a small demo at the end:

Once again, I really hope someone will find this useful and do not hesitate to ping me in Twitter to share your experience or even better, a link to your own take at this "feature".

As for the WSL, Azure and Docs teams: please continue to bring such cool features, I will keep having these crazy ideas on how to connect them :)


>>> Nunix Out <<<

Comments

Post a Comment

Popular posts from this blog

WSL: One Home to host them all

Introduction This blog post will explain how a single home mount can be shared accross all  the WSL instances. It was quite fun to find the idea and then make it happen. It will use all the tools currently available from WSL, so please don't expect a "Linux only" as Interopability will be heavily used. And before I start, here is my point of view about WSL: It's not only  Linux! It's different, just like GNU is different from Unix (yes I said it). We have finally the strength of both worlds combined. And while I do understand the "dev" aspect is meant to be reproducible in a Linux prod environment, the "ops" side is meant to take advantages of everything that can make the full environment feeling Home. Setup requirements In order to really enjoy this solution, I do recommend having 2 or more WSL distros installed or, if you fell like a real WSLCorsair, try @bketelsen crazy setup (I love it)! While the distros are downlo
3 comments
Read more

Docker + WSL: Get 2 daemon for the price of 1

Introduction almost two years ago, Docker announced the capability of switching between the Linux and Windows containers "mode" (far from the right click that we have today). At that time, I wrote a blog post on how to run both daemons at the same time ( http://darthnunix.blogspot.ch/2016/10/docker-for-windows-2-daemons-enter-in.html ) Fast forward to 2018, and while we were blogging on how to get the TLS connection from WSL docker client with  Rory McCune  ( https://raesene.github.io/blog/2018/03/29/WSL-And-Docker/ ), another blog post, by Stefan Stranger drew my attention (read: blew my mind) as I was trying to reproduce the same: how could I "bind" the docker socket in WSL with the Docker for Windows Linux mode socket ( https://blogs.technet.microsoft.com/stefan_stranger/2018/04/02/access-my-docker-for-windows-kubernetes-cluster-from-debian-wsl/ ) From 1 to 2 daemon: DemonHunter mode achieved Now that we have all the required setup resources, let's b
4 comments
Read more

VSCode + WSL: the SSH way

The initial idea early 2017, Rich Turner made a demo where Visual Studio was used to develop C++ code, however the debugging environment targeted was WSL! With some magic, he showed something that he had forbidden from the initial release of WSL: writting directly to the WSL filesystem (still a big no-no actually). Of course, this triggered a lot of curiosity and the WSL Corsair had to loot from it too! SSH to save the day the biggest challenge was to find a way that not only could be easy to setup on both ends, and also would be approved  by the WSL team.  TLDR: if you use the Windows Path, You Die! #ThereBeDragons Another way, more Linux-oriented, needed to be used and hopefully a solution already existed and was simply waiting on being used: SSH🔐 The setup the setup is done in 2 distinct parts: Setup the SSH server on WSL Setup the SSH client on VSCode  While the SSH server is a standard procedure in Linux, finding the right  plugin for VSCode was a bit more chall
Post a Comment
Read more