Starting in Windows Insider build 17093, a WSL application can communicate with a Windows application over Unix sockets. Back in December, we blogged about bringing AF_UNIX to Windows. Now, we’re building on that functionality. Consider a requirement where you want to run some kind of service as a Windows application.
We’ve added new file system features to WSL in Insider Build 17063. You can now set the owner and group of files using chmod/chown and modify read/write/execute permissions in WSL. You can also create special files like fifos, unix sockets, and device files.
Hey WSL users—we have more features to share with you! Our latest Windows Insider build lets you share environment variables between WSL and Windows. Starting with Build 17063, let’s look at how you can leverage the new “WSLENV” to enhance environmental variable interop between Win32/WSL.
Beginning in Insider Build 17063, you’ll be able to use the unix socket (AF_UNIX) address family on Windows to communicate between Win32 processes. Unix sockets allow inter-process communication (IPC) between processes on the same machine.
Support for the unix socket has existed both in BSD and Linux for the longest time,
We frequently get asked about running docker from within the Windows Subsystem for Linux (WSL). We don’t support running the docker daemon directly in WSL. But what you can do is call in to the daemon running under Windows from WSL.
Starting in Windows Insiders Build 17046, WSL supports background tasks (including daemons). In the past, if you opened WSL and started sshd, httpd, screen, or tmux you needed to have a console window open to keep those tools running. But, starting with 17046,
There are a variety of ways to invoke the Windows Subsystem for Linux from Windows commandlines and they all behave a little differently. Let’s get to the bottom of it.
The first (and recommended!) method will start up your default distro.
Dear friends of WSL (Windows Subsystem for Linux, nee “Bash on [Ubuntu on] Windows”) & Windows Console:
I would like to share with you some changes to our org’ that will benefit WSL, Windows Console and the Windows command-line in general moving forward.
When Windows 10 Anniversary Update (AU) was shipped, the Windows Subsystem for Linux (WSL) was still far from complete, and was known to have many incompatibilities, especially with popular developer tools like node.js, Java, etc.
However, it was important to get this exciting new feature into the hands of real users so that we could learn from them –
I first learned about Visual C++ for Linux, which was released in March 2016, shortly before the Windows Subsystem for Linux (WSL) was first announced. I was immediately blown away by how VERY cool this feature of Visual Studio is!
What’s insanely cool about this feature is that when the project is built,