3 ms·
Lack of virtualization and container support within the WSL was a major blocker for me, has this been resolved?
by gshulegaard 7y ago
Lack of virtualization and container support within the WSL was a major blocker for me, has this been resolved?
- Lendal 7y agoWSL2 offers Docker support. It will be included in the next update of Windows. Many people are using it now but I don't have time to mess with beta software. I am exercising my patience.
- m_mueller 7y agoI'm also a bit disappointed it doesn't bridge the host network like WSL1. It's nice there that I can just run something and access it on local host - it even works together with docker-for-windows, the docker CLI client being in WSL.
- DuskStar 7y agoI believe that recent(ish) builds of Windows, webservers running in WSL can be accessed from Windows via localhost:port, just like with WSL 1. [0] Accessing servers running on the Windows side from WSL is a fair bit harder, but IMO also a lot less likely. 0: https://docs.microsoft.com/en-us/windows/wsl/wsl2-ux-changes#accessing-linux-applications-from-windows https://docs.microsoft.com/en-us/windows/wsl/wsl2-ux-changes...
- m_mueller 7y agoOh that's great news. Thanks!
- battery_cowboy 7y agoEverything is transparent to me, it's like I'm working in Linux when I use vscode and wsl2 together. There is still the issue with dbus, but you can get a script that replaces sysctl to her things running again. Edit: to be specific, I can access local servers on wsl2 from windows, I don't even use an xserver.
- m_mueller 7y agoalmost same here, only it's WSL1 + vscode.
- fovc 7y agoHave you tried running docker on windows directly? There's a bit of network fiddling, but you can then use the docker client from wsl
- rraghur 7y agoI'm still on wsl1.. and just ran into this today.. you can run docker for windows and the docker client on wsl can access it over tcp For docker composer i had to change the root in wsl.Conf