Or: How do i work in a modern, efficient and really really nice way?
The goal of this article is to set up a system where you will be running an angular web application in WSL2 and access it via a Browser on the Windows Host. It’s pretty straightforward, because i prepared a little something.
Prepare following docker-compose.yml file (which you want to place somewhere on the same file-system level as your application, or above it, not below!)
You WILL have to fix the indentation to match yml standards.
You might notice that we are using an existing image from the docker hub. It’s actually a repository that i manage and maintain with a friend. If you check it out in detail, you will notice that this images matches the latest angular-web-development standards as per november of 2021 (nearing the end of the corona crisis, probably, maybe).
The image basically uses Node:14 as a base image, containing NPM and YARN, and installs Angular-CLI 13 and Angular-Core 13 on a local and global level, then exposes port 4200.
THIS IMAGE ASSUMES THAT THE DOCKER COMPOSE FILE IS ON THE SAME LEVEL AS THE APPLICATION DIRECTORY & THE APPLICATION DIRECTORY IS NAMED “MY-ANGULAR-APP”
Of course, you can easily modify the “ports” section of the compose file to change the port you want to serve to, the LEFT side is the host side.
That means that if you run this compose file with a valid application, you will be able to reach your application from a browser on the windows host via “http://localhost:4200”. If you change the LEFT element from 4200 to 4201, the address will be “http://localhost:4201” independently from the actual EXPOSE command in the dockerfile providing the container.
This command assumes you have a proxy.config.json in the application directory, remove the –proxy-config proxy.config.json part if you do not have a backend running on the windows host, else, create a proxy.config.json and configure it to lead to the windows host.
The npm command will install all dependencies whenever the docker-compose has been run.
Now, if you also want to be developing in visual studio code, install it in your WSL and run “code path-to-your-app-directory/. “ it will open VS code in this directory, vs code will automagically understand that this is an angular application and will give you some prompts depending on its complexity and components.
If you now have a valid application in the “my-angular-app” directory, you can have fun and start developing.
Of course you will choose the folder where you put the script. don’t forget to add quotations if your path contains spaces!
Click next and after finishing the setup open the Task back up again. (Edit properties)
In the General Tab set “Run only when user is logged on” and “Run on highest privilegues”
Open the Trigger in the “Triggers” tab and set a Delay for 1 minute.
That’s it! Have, of course you will have to chill about a minute or two after rebooting your pc. If you’re faster than your scripts, this won’t work. You might also want to adjust the delay time for the script for part 1. and 2.
Or: “I don’t want to manually startup everything in WSL after every boot”
For me, that’s docker. My docker is running independantly of docker desktop on the host so i want it to startup when the PC is booted.
Following easy steps to set it up in Task Scheduler:
Open up Task Scheduler
Create new Basic Task
Name it like you will, mine was “Autostart of WSL Docker service on boot”
Next, then choose “When the Computer Starts”
Next, then “Start a program”
In “Program/script” find WSL.exe, it should be located like so: “C:/Windows/System32/wsl.exe”
In “Add arguments (optional)” enter following: -d Ubuntu-20.04 -u root service docker start
Finish the setup via “Next” then “Finish”.
Run it to test it.
Instead of “Ubuntu-20.04” you might want to find your correct distro name by entering “wsl –list” into a commandline on windows, you’ll need to use the same distro name displayed for the distro of your choosing.
Edit: if this doesn’t immediately work for you, you might want to open up the task in task-scheduler, navigate to “triggers”, open the trigger and set “Delay Task for” to 30 seconds or any amount that makes sense for your system start-up time.
Or: “Get Docker running in WSL without WSL Integration”
Recently, i’ve had a special case where i had to develop a project with Docker containers running on the Windows Host Docker, other containers running in WSL and some of the tools running directly on the Windows Host. (Basically, a big confusing mess).
To get this 3-way-communication going, i actually had to install Docker in WSL independantly from Docker Desktop on my Host. This turned out to be a little tricky, just because i didn’t really know where to look up the sources.
So if anyone of you have these special needs, feel free to follow me along. Take these steps:
Install Docker Desktop normally on your host, do not enable WSL Integration but install all tools necessary for WSL Integration (just in case)
As i don’t know if the site content ever changes i wanted to have a copy of the steps myself.
Now you have docker only in wsl, you will have to start up the service manually if you open up your WSL instance for the first time or if WSL is stopped completely. But i’ll offer a fix for that later.
This will also work without Docker installed on the host, so both instances don’t know about each other and Docker Desktop cannot f* with your network too much.
(For people who like to hibernate/sleep rather than reboot.)
So after keeping you machine running for some days, weeks, or in unlikely cases maybe months without a reboot, you might notice that wsl has trouble retrieving packages from the web and maybe even other strange problems.
This might be related to “clock skew”, an issue where the clock in WSL (2) desynchronizes with the host clock.
There’s an easy fix which sadly requires you to run a sudo-ed script in wsl on startup.
I keep forgetting to start the docker service when opening up an instance of WSL(2)
Let’s fix that!
So what do we want to do? We want to run the docker service from startup! And that has to be done on sudo… but we don’t want to be reminded of that constantly (in the form of a prompt to enter the sudo password on every WSL2 instance start).
First of all, sadly, we need to stop WSL from asking us for the sudo password.
WSL2 normally is being used during development, ideally by a person that actually know what they’re doing, these people – and developers – sometimes have to run scripts on wsl startup or keep having to start services manually running sudo.
This can be time consuming or even hinderance at worst. To circumvent this issue, you can stop WSL from asking you for the sudo password.
I know that this is not the best possible thing you can do security-wise, but i’ve been looking for a lot of possible ways to work around auto-sudoing and could not come up with a satisfactory solution, especially if you are the type that keeps hibernating the PC instead of rebooting (like me) so WSL never actually has to restart at all.
This imposes a security risk and enables scripts running on user-level to be executed with higher privilegues, please only do this if you actually know what you are doing. Personally, as WSL is a development environment, i find the list pretty low, but that also depends on what kind of packages you download and what kind of data you handle on your machine, especially because WSL enables access to the windows file system!
Anyway, straight to the point: To stop WSL from asking you for the SUDO password, open up a WSL (2) Shell and type
And add the following line to the end of the file
YourUsername ALL=(ALL) NOPASSWD: ALL
Of course you will want to type in your username instead of “YourUsername”. Then press Ctrl + O and exit the window. After the next WSL startup you should be all set-up.
While working on a project employing a Client in WSL 2 (Windows Subsystem for Linux) and a Web-Api running on the Windows Host i noticed that there are several complex issues to resolve to get the communication going. The main issue was that the connection between these two instances was hard to establish and needed lots of maintenance after each reboot or network reconnect of the machine which the ecosystem was running on.
It’s hard to set up a connection between WSL2 Docker and Windows Host/Windows Host Docker, a solution is to employ a Reverse proxy on the Client in WSL2 Docker and prompt the Windows Host Server to listen to the WSL Adapter IP Address.
TALK FROM LINUX
(SUBSYSTEM FOR WINDOWS)
The first task is to set up the WSL Adapter IP Address for your reverse proxy client-side in wsl.
Run a WSL2 Terminal, from your current (home/default) directory, run sudo nano .bashrc
Now, when you run your docker container in WSL, pass the environment variable WSL_WINDOWS_HOST
for example using this parameter (or a docker compose): -e APIHOST=$WSL_WINDOWS_HOST
Inside the container, you just have to configure the proxy to use
http://$APIHOST:[YOURPORT] (or https of course)
Well, that’s done, now the WSL Container wants to talk to Windows, but nobody is listening, story of my life, let’s fix that up.
LISTEN FROM WINDOWS
The second task to get this running was to notify the Application about the WSL Adapter IP Address. If you want to see the WSL Adapter IP Address just type “ipconfig” in powershell and find the WSL Adapter IPv4 Address.
You would want to inform your Server Application on the WSL Adapter IP Address, it needs to listen to this to receive connections from WSL.
To employ this IPv4 Address (make the Server listen to it) you want to change your launchSettings.json to listen to “http://[YOUR WSL ADAPTER IP ADDRESS]:[YOUR PORT]”
BUT: The WSL Adapter IP Address changes on every Windows Host reconnect to any network and consequently on every reboot and/or occasionally on wake-ups of the Host system (from Sleep or Hibernate). Normally, the IP-Address to listen to has to be configured in your (server) application, that means that you have to set it before the server application starts. If the IP constantly changes, it can be time consuming to look up the WSL Adapter IP Address every time and change the server settings accordingly.
Well that’s where Task Scheduler and Powershell play together, you will want to create a powershell script that reads the WSL Adapter IP Address and stores it in an environment variable, this environment variable can then be used by your server application.
Luckily, i took the time to figure out the Powershell and corresponding Task Scheduler settings:
This is the powershell script, here called “wsl_adapter_ip_to_env.ps1” and located in “C:/Sources/Scripts_Autorun” on the Windows host:
Create this file and open up the Task scheduler (Windows Key + R, then “taskschd.msc”)
Create a folder in the Task Scheduler Library (for better Script management), i created “Task Scheduler Library/WSL_DEV”
Create a new Task (NOT a Basic Task) with following Settings: GENERAL TAB: > Description: “Create ENV Variable WSL_ADAPTER_IP with WSL ADAPTER IP Address” > Security Options: Run only when user is logged in (your user) > Security Options: Run with highest privilegues
TRIGGERS TAB: > NEW TRIGGER: At logon (your user), Delay: 1 minute, enabled (this will update the WSL Adapter IP variable on logon) > NEW TRIGGER: On an event (basic), Log: Microsoft-Windows-NetWorkProfile/Operational, Source: NetworkProfile, Event ID: 10000, Enabled (this will update the WSL Adapter IP on every Windows Host Network reconnect, no matter which adapter or network type)
ACTIONS TAB: > NEW ACTION, START A PROGRAM Program/Script: powershell Add Arguments: -windowstyle hidden -ExecutionPolicy Bypass -file C:\Sources\Scripts_Autorun\wsl_adapter_ip_to_env.ps1
That’s it, now you will have an updated WSL Adapter IP Address Environment variable every time it changes.
There are multiple approaches to use this environment variable in a .Net API, currently i’m doing this in “Program.cs”
public static IHostBuilder CreateHostBuilder(string args)
string wslAdapterIp = Environment.GetEnvironmentVariable("WSL_ADAPTER_IP");
Console.WriteLine("WSL_ADAPTER_IP Environment variable is set, using.");
Note that you will need to pass this environment variable into the container via the “-e” flag or a docker-compose file, this example will work directly on the host using the env var that has been set by the task scheduler.
Well then, happy coding, leave a like, comment or whatever, until next time and don’t forget to bash in the bell icon and call the foo fighters. Bye!
(As usual, i’m open for constructive criticism, fixes and anything else that you might want to contribute)
If WSL-Integration is active in Docker Desktop, none of this will work. Disable WSL-Integration under Docker-Desktop Settings -> General
This also implies that you install docker on your WSL (2) the same way as you would on a seperate machine.
Another important finding!
This setup worked for me for a few weeks, then suddenly stopped working.
I put some hours of figuring-out into it and noticed another problem:
It seems that the network settings are scrambled/broken when Docker Desktop starts before WSL2 – Docker.
That means that if Docker Desktop is started on Windows Startup as usual, WSL Docker will be unable to talk to the Windows Host.
To fix this very strange behavior (please somebody take the time to explain this to me?) i have 2 workarounds:
Disable Docker Desktop autostart and run only after WSL 2 Docker has been started.
Please note that the bashrc script on WSL will only run if WSL is starting, this means that if the WSL Adapter IP Changes during runtime, you need to restart WSL by closing all Windows and opening a new one or by rebooting the machine if you prefer.
Please note that Windows works in strange ways, for example, if you open a command line window or start a process, on start, the process will load all environment variables and not update them (ever, again), this means that if you are running Visual Studio or a Command Line and your Adapter IP Environment variable changes, you might want to restart Visual Studio or the Command window.
These behaviors cannot be influenced by me and are operating system dependant quirks, i’m already looking into some kind of force-reload mechanisms, but other than working with temporary files (which is NOT a good way) i could not yet come up with a solution for VS or WSL (though i found a force-reload for cmd/ps).