According to Kali as of March, WSL does not support raw sockets. That doesn't mean that Metasploit isn't useful, however, as there's at least one exploit (NSA Equation Group's EternalRomance) tutorial designed for use within WSL.
>Is the subsystem a separate, distinct entity from my normal windows environment?
Yes, You need to install node separately in your wsl environment.
I prefer this way to install it.
>The project we're working on requires a development environment using VS Code, Node, MongooseDB, and Express.
The best way to do this would be to install the remote development vscode extension, which I believe is available only for vscode insiders build. It allows you to use the wsl environment with all vscode extensions support.
Then install mongoDB in wsl and use npm in wsl to install mongoose and express.
You can run many Windows applications in Linux; Wine has been a thing for 10+ years now. It just doesn't work very well. There are variants of it that are specifically for gaming, Valve's Proton is state of the art I think. You're exactly right why Microsoft is not excited about this technology. Windows OS is the core platform for the whole company.
I am a macOS refugee, since last year, after purchasing a new MacBook Pro 13" with keyboard issues and receiving poor customer support experience!
Windows 10 supports virtual desktops, so this guide might help for people interested in using them: https://m.windowscentral.com/how-use-multiple-desktops-windows-10
I was using ConEmu with Ubuntu on WSL, but found ConEmu really slow and always using a lot of CPU (30% CPU usage), which I find unacceptable, so I've decided to switch to Hyper (http://hyper.is).
While it does use a good amount of RAM, it doesn't bother me, since I have 24GB in my ThinkPad T470s.
As for Docker, I'm using Docker for Windows in combination with the docker client in WSL, and overall I'm really pleased with the result.
For my use case, I mainly work inside Ubuntu on WSL, which answers all my needs for having good command line utilities in Windows and give me an even better experience than macOS, since WSL is a Linux userland environment with up-to-date tools.
As for simplifying my setup, when I need to reinstall my laptop, which doesn't happen often, but still, can happen, I put all my configuration files inside my Google Drive, which is synced using Insync. My WSL bashrc, SSH configuration, and Hyper configuration files are all symlinked, so that they are automatically backed-up on change.
>> Package management (like Homebrew on Mac)
>Nope, or nothing that I am aware of. Closest thing i would suggest is Ninite, but it is not as complete. Should be enough for most standard users, not sure if it will fit your use-case.
Check out chocolatey
> If you are using git for Linux and use a Windows editor then it'll hose the permissions which will lead to the next commit containing a lot of permission changes which you don't want.
https://stackoverflow.com/questions/1580596/how-do-i-make-git-ignore-file-mode-chmod-changes
> git config core.fileMode false
We can find it if you share your motherboard manufacturer, we can see what kind of bios it has and look it up in the docs for you.
​
Do you know what motherboard you have? You can look it up with cpu-z https://www.cpuid.com/softwares/cpu-z.html
You should configure your git according to this: core.autocrlf.
Essentially you set git in Windows to
$ git config --global core.autocrlf true
and git in WSL to
$ git config --global core.autocrlf input
Then git will handle your line endings for you.
> so I wouldn't pay $6 for it at this point. But maybe future development will allow it to surpass those products.
The big question is will the author be regularly maintaining that package. The Xming author is releasing update an update about once a month which includes updates builds of various tools, and fixes for various issues.
If this app is $6 and that will be actively supported it may be a good deal. But if it is $6, and it won't be maintained, IMO it isn't worth paying for. The Xming has a history of maintaining the package for 10+ years now.
> I think that Xming is abandoned, and XcXsrv still has support.
Xming isn't abandoned. Last release was May 27th, 2018. But the person that maintains it now releases as 'domationware'. IE you have to 'donate' to download. Think of it like a patreon style arrangement where the 'donors' are sponsoring this person to maintain the package.
They are currently asking for 10 GBP or about $14 USD for a years worth of downloads.
I'm using Cmder, which is an enhancement of ConEmu. It's not a full GUI, it's a Windows Console app, but it does xterm emulation. I'm not thrilled with it but it works pretty well, with some visual quirks at the margins.
SecureCRT used to be my favorite terminal program for Windows back in the day. It's still around, I haven't tried it in awhile. It costs money.
Not a Ruby user myself, but I know that VS code doesn't natively see WSL environments the same way that it sees Windows environments. You might have to use this experimental new feature: https://code.visualstudio.com/docs/remote/wsl
Not sure how you were able to get it working with Atom -- I thought Atom had the same limitation, but maybe they've implemented some kind of workaround
He's using tmux for the split terminal screens, for the system stats i'm sure he's using htop, for the cows cowsay.
If you are looking for the app to communicate with the WSL instance, it looks very similar to FluentTerminal ( https://github.com/felixse/FluentTerminal )
If you don't need any specific Windows software, have you considered going for a Unix distribution instead?
> Keyboard shortcuts for Mac user hands (I can't get over feeling the Ctrl key is only for control characters)
I had the same problem when I had to use a Mac at work. AFAIK, there is no proper way to rebind them for every piece of software, except by editing the registry, which does sometime lead to unexpected results.
> Package management (like Homebrew on Mac)
Nope, or nothing that I am aware of. Closest thing i would suggest is Ninite, but it is not as complete. Should be enough for most standard users, not sure if it will fit your use-case.
> Cruft management (uninstalling apps, registry, #FML)
Check GeekUninstaller. Do not trust the built-in windows uninstaller, it does not clean registry, nor does it clean temporary and config files.
> A terminal that doesn't suck
Not the base terminal with Windows command line. I use Putty to connect locally to WSL, which does work without hogging tons of CPU, but looking for alternatives, as I had to do lots of tweaking to get the older version on WSL to run headless. I do remember WSL patch-notes saying that had been corrected, but i'm too lazy to upgrade to the current version.
> Docker
Used it for work, was not too much of a pain to setup, ran decently.
xlaunch.exe
echo "export DISPLAY=:0.0" >> ~/.bashrc
sudo sed -i 's/<listen>.*<\/listen>/<listen>tcp:host=localhost,port=0<\/listen>/' /etc/dbus-1/session.conf
sudo chown -Rv $USER:$USER ~
exit
https://github.com/microsoft/winget-cli
It works, but it's just an installer-executor like Chocolatey rather than a package manager like Scoop. Still, if you have installed stuff with their installer, Winget will work just fine to update (aka reinstall) them.
Sorry. I thought I got it to work.
But while collecting information for the post I found that "sudo" failed. In a nutshell, I downloaded the february version of the ISO, applied the manual stuff listed here https://www.archlinux.org/ At some point I had to add a Russian dude's key manually in order for all the packages to install.
For the post, I was trying to install from the April version at it means less manual stuff to do.
Russian dude's key:
# pacman-key --lsign-key 753E0F1F # pacman-key -r 753E0F1F
So, I did get Arch to run, but when running sudo I get:
sudo: getrlimit: Function not implemented sudo: setrlimit: Function not implemented sudo: setrlimit: Function not implemented
Without sudo, su is your friend.
With "pacman -R linux" I got rid off a lot of i-node errors: "large inode number truncated: Numerical result out of range"
They have Ubuntu versions of Sublime Text prepackaged, so you could run:
wget https://download.sublimetext.com/sublime-text_build-3114_amd64.deb
which would, in this case, download the 64 bit version of ST3. You can copy the link for the other versions if you choose.
After you download the deb package, you install it with
sudo dpkg -i /path/to/deb
First you will need to install xorg with sudo apt install xorg
Second, you will need an x server on Windows. I use VcXsrv but there are a few others.
Once you have both of those, start your x server on Windows. There's a small setup process the first time. Then in Bash run
DISPLAY=:0 subl
You may run into some dependency issues with Sublime, but they can be solved by apt installing some libraries (for me it was sudo apt install libgtk-2.0
and that installed all of the other libraries that were missing.)
Firstly, your first screenshot shows you didn't finish the download and installation process. Its still asking you to proceed.
Second, you say you don't think it worked but won't tell us why you think it didn't work.
Thirdly, the code and error you show seem to have nothing to do with bootstrap but with image loading. So what do you want?
Lastly, if you don't know how to include files (yet), and are just trying stuff out, why not use the bootstrap cdn? https://getbootstrap.com/docs/5.1/getting-started/introduction/
[edit] Also that bootstrap package seems very outdated.
You can create a "global" launch.json by inlining it in the launch
field of your user settings (it will be ignored in projects/workspaces with a launch.json)
https://code.visualstudio.com/docs/editor/debugging#_global-launch-configuration
Unfortunately you can't do the same for tasks.json, though it's "on the agenda"
From your reaponses here it seems you are using the default terminal, which is called conhost and not like someone else said "cmd.exe".
Theme information for conhost is stored in the registry and you can edit it yourself or import other peoples themes as a .reg file.
Another option is to use ColorTool which allows you to import iTerm2 themes which you can find many of because iTerm2 is a very popular Mac terminal.
Then use ColorTool to import this: https://github.com/mbadolato/iTerm2-Color-Schemes/blob/master/schemes/Gruvbox%20Dark.itermcolors
The backslash could be related to AltGr issues? Looks like it could be resolved soon.
Also there is multipane support in the works, but I haven't tried it and it may not have a default keybinding.
D'oh! Yeah, pretty obvious what you meant... once you point it out.
You can still compile the terminal yourself from the github repo. They've simplified the process considerably from the original commits. All you need is Visual Studio Express or Community... whatever the free version is called at the moment.
ah, my bad. I got confused then with enabling Hyper V. You are right, I was referring to enable virtual machine platform.
I followed this guide and the issue happens after running this line: dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
I restart the laptop after that and then I got the BSOD unless I disable Iris Plus Graphics Driver.
explorer.exe and look for the Linux icon on the left panel ??
https://www.omgubuntu.co.uk/2020/04/access-wsl-files-windows-explorer
I now do like /u/WSL_subreddit_mod said with symlinks to Windows directories that are synced with OneDrive for work (I also have an alias for rm -r that pops up a warning to check there's no symlinks in the directory I'm removing bc I'm often a dope ha ha), but when I used github to do this I found my proficiency with the github system grow by leaps and bounds. Personally, git stash became my BFF during that time.
I haven't installed apache or mysql on my WSL install yet, primarily as I host on an old Mac.
I did find this step-by-step guide for Xenial, though:
This link, under prerequisite number 1.
I read that, then did some searching on Discourse running on Ubuntu in WSL, and from there found suggestions for running different server instances, but not much more than that.
I installed VS Code Insiders as well, which also fails to do any linting or syntax highlighting.
It pretty much fails to do any of the ascribed features noted here:
This may be because you're trying to modify ~/.bashrc
without being properly "inside" the WSL distro. I'm not sure exactly what your issue may be based on your comment alone.
Follow this tutorial to configure VSCode for remote access to your WSL distro. This should allow you to "attach" to the distro, giving you native access to the filesystem. At that point, you should be able to "Open Folder" /home/<user>
(aka ~
) and then click on .bashrc
to edit it in the VSCode interface.
It's a home computer, I had NordVPN installed but I uninstalled that with everything that comes with it just to be sure, but as soon as I switched to WSL 1 from WSL 2 it started working, so I'm not even sure what could be the problem at this point.
I reinstalled WSL and Ubuntu before trying it again and that was having the same result where nothing would happen with Copilot, switching to WSL 1 though just gets it to work, so it's a bit of a confusing one because I'm not sure why a fresh Ubuntu install on 1 would work, whilst it won't on 2.
You can install winget which allows you to winget uninstall cortana
for one. You can install your favourite software like you can with ninite.com and even keep it updated with winget upgrade --all
.
Did it on Ubuntu :)
Added and installed wine1.8 from PPA: https://launchpad.net/~ubuntu-wine/+archive/ubuntu/ppa
started wine64 cmd from normal user (!) (fails as root)
64bit apps are working fine, proof: :)
If you want native windows, cmder is one of the better ones (though it has the same color and unicode problems, but the performance is way better).
Or you could just install vcxsrv and install pantheon-terminal like so:
sudo add-apt-repository ppa:elementary-os/daily && sudo apt update && sudo apt install pantheon-terminal
However, you will need to invoke pantheon-terminal from a bash prompt since WSL has a problem with invoking stuff with gui, but hey, it has everything you expect a linux terminal to have, so there's that.
The main thing you are giving up, and it is a pretty big thing, is the VS Code integration between windows VS Code, WSL 2 and Docker. It is a really nice experience.
https://code.visualstudio.com/blogs/2020/07/01/containers-wsl
Also, if you're not wedded to the Jetbrains tools, I'd look at VS Code. There are integrations that make it very easy to develop in WSL without the need of an X client.
You hadn't yet mentioned VSCode :-)
I suggest you read this: https://code.visualstudio.com/docs/editor/debugging#_launchjson-attributes
Or maybe better still, there is a WSL extension for VSCode which may help to do what you're asking.
The main problem I think would be performance, I've been looking into I/O performance of NFST and it's pretty bad, feel like an ext4 partition could do the job too especially if I'm running Visual Studio Code with WLS support to access those EXT4 partitions within Windows.
https://vxlabs.com/2019/12/06/wsl2-io-measurements/
https://code.visualstudio.com/blogs/2019/09/03/wsl2
Maybe I'll add a NFST partition for general file sharing, music videos etc. 🤔
You can set git to temporarily cache your credentials for a set period of time.
Example:
git config --global credential.helper 'cache --timeout 3600'
More info: https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage
I've seen that bug report but it's a mess with no straight answers and a lot of stabs in the dark.
Surely someone knows how to get more details. I added debug
to the kernel parameters but that didn't produce any more detailed output.
possible solution:
cp /mnt/<drive>/path/to/key/{id_rsa,id_rsa.pub} ~/.ssh/ && chmod 600 ~/.ssh/id_rsa
you could try to ln -s too, but I don't know how permissions are handeled then. I'd rather copy the key into wsl.
here is a SO thread you might like
echo "export DISPLAY=:0.0" >> ~/.bashrc
sudo sed -i 's/<listen>.*<\/listen>/<listen>tcp:host=localhost,port=0<\/listen>/' /etc/dbus-1/session.conf
sudo aptitude install gnome-terminal
sudo chown -Rv $USER:$USER ~
gnome-terminal
https://nodejs.org/en/download/ install a new version on WSL.
You should never run Windows node in WSL 2 environment, it'd be slow.
Also you can use which node to see where is the node you run.
But I'd recommend using version manager such as nvm, asdf or any other.
👆 This, but I would replace the code editor in WSL via X Server with the RemoteWSL extension for VSCode. Been using it like this for a couple of months and it is really seamless.
You have to install Visual Studio Code first, naturally.
And I just tested calling it and I didn't need to sudo at all.
I runs for me as default user just fine on Ubuntu.
In case someone wants to use their virtual environments with VSCode and WSL, this has been fixed in WSL2, so it is possible now to use it natively:
VSCode remote development: https://code.visualstudio.com/docs/remote/remote-overview
This will let you reopen your project within WSL.
Note though, you need to set up the project within WSL rather than Windows. Assuming you're using source control you should be able to clone down into WSL and work from there.
It was more for the starting path. code isn't in your path. Do you simply need the code .deb installed? https://code.visualstudio.com/docs/setup/linux
Maybe booting with "OS Boot information" in msconfig.exe Startup-tab could be useful.
And since you don't get BSOD, I guess BlueScreenView will show nothing at the moment.
I am running win10 pro + debian WSL1 + a chocolatey install of wsltty: https://chocolatey.org/packages/wsltty
I experienced this same error this morning after a win update. I managed to fix it by:
This was a low-friction way to put this out of my mind until I decide I want to see what WSL2 is all about.
Do you have acrylic installed? If so, it has small software where you can disable or enable the acrylic service.
to install: https://sourceforge.net/projects/acrylic/
using chocolatey: https://chocolatey.org/packages/acrylic-dns-proxy
I definitely have Docker running. docker run hello-world
worked worked as expected. Instructions are in this section: https://kubernetes.io/blog/2020/05/21/wsl-docker-kubernetes-on-the-windows-desktop/#docker-desktop-settings-enable-wsl2-integration
Kind of an odd way to install it though. Does the normal installation create a systemd service?
So for windows I use https://www.voidtools.com/ Everything which is a nice and very fast indexer that sits in the system tray and indexes in real time so that it's always up to date
https://i.imgur.com/jTmQf2q.png
It's got a dozen features I never use but it's a great "replacement" for locate on windows (except like most windowing tools, it makes it hard to use in some pipeline like command tools like locate can do)
I really want only my stuff indexed on wsl, so my /etc/updatedb.conf looks like this:
PRUNE_BIND_MOUNTS="yes" # PRUNENAMES=".git .bzr .hg .svn" PRUNEPATHS="/tmp /var/spool /media /var/lib/os-prober /var/lib/ceph /home/.ecryptfs /var/lib/schroot /mnt/c /mnt/d /mnt/host /mnt/host" PRUNEFS="NFS afs autofs binfmt_misc ceph cgroup cgroup2 cifs coda configfs curlftpfs debugfs devfs devpts devtmpfs ecryptfs ftpfs fuse.ceph fuse.cryfs fuse.encfs fuse.glusterfs fuse.gvfsd-fuse fuse.mfs fuse.rozofs fuse.sshfs fusectl fusesmb hugetlbfs iso9660 lustre lustre_lite mfs mqueue ncpfs nfs nfs4 ocfs ocfs2 proc pstore rpc_pipefs securityfs shfs smbfs sysfs tmpfs tracefs udev udf usbfs"
As for indexing windows, I let Everything https://www.voidtools.com/ do that
I've got rootless podman running on WSL/Fedora 34. I saw your errors, too.
I don't remember the exact steps, but I pretty much followed https://dev.to/bowmanjd/using-podman-on-windows-subsystem-for-linux-wsl-58ji
Can I ask how you got docker installed and configured on Ubuntu 20.04?
I just tried it on a fresh Ubuntu 20.04, using these instructions and it seems to work. I did have to edit my resolv.conf file, but that is likely unrelated to your issue.
Alternatively, you could have a go with podman on WSL. It is a daemonless replacement for docker.
https://github.com/Microsoft/vscode/issues/65036
tldr: add the following setting:
"window.titleBarStyle": "native"
https://code.visualstudio.com/docs/python/debugging#_remote-debugging
You still need a Python install on the Windows side. Depending on your requirements, you can also just have a virutalenv for all of the requirements in it, but you just do not run it in Windows, only WSL. This would allow for all of the linting and IntelliSense features as well. -
No, I briefly tried to follow the instructions I found to do this:
sudo apt-get build-dep python3.5
But this doesn't work since there is no python3.5 in Ubuntu 14.04. I think I either need to find a ppa for it, or get them individually - looks like they are listed here: http://www.linuxfromscratch.org/blfs/view/svn/general/python3.html
I thought VcXsrv was derived from Xming, so a lot of the documentation for Xming applies. See http://www.straightrunning.com/XmingNotes/
That being said Xming documentation is also poor. I had to go through a bunch of different pages over a few day to figure out what flags did what and how to run it correctly. Then X410 went on sale in the Windows Store and I used that instead.
I don't understand what you are trying to do. If you want to run a normal X server, you need a device to display to and Windows doesn't offer that to Linux apps. The best that may be possible within Ubuntu on Windows is to run Xnest, Xvnc or something like that, which connects to a native Windows app.
At http://www.straightrunning.com/xmingnotes/ it seems you either need to download an old version or "donate" to obtain a password to download a newer version. I guess VcXsrv is a better alternative.
So, install VcXsrv in plain Windows, and some X11 apps in Bash, like sudo apt install leafpad
, installing dependencies also. Then run VcXsrv, tell Linux apps to use it via export DISPLAY=0:
in Bash, and finally run the X11 app, eg. leafpad
. It simply works.
Don't leave an X server with no authentication open to external incoming connections though. That's a gaping security hole. Block it at the Windows firewall at least.
<strong>Console2</strong> has hotkey customization support. Here's a rundown/default config setup with hotkey changes and more that might be of interest: https://www.hanselman.com/blog/Console2ABetterWindowsCommandPrompt.aspx It's a shame that development stopped in 2011.
I'm a current Cmder user and my goto, but there are aspects of both it and ConEmu beneath it that still bother me, like user aliases for one, and really want to see some serious competition.
I'm sure there's a way to get it working in bash, but you may want to consider checking out zsh and on top of that add ohmyzsh. (I think tab completion is part of ohmyzsh, but I've never really used raw zsh enough to remember.)
With that setup, tabbing when there are multiple matches will allow you to tab scroll through each selection and hit enter to select it.
I just used this link; I used the curl-based command under 'getting started'. It asks if I want to replace my shell, and after agreeing and restarting, I've got a new shell.
There is a project called Darling, it is a Darwin environment for Linux, but it could be run on WSL2 too. See this issue comment for more details.
I mean if you ask a vague question without the showing that you have done the basic Google searches you are going to get the same results on almost every forum.
At some point it is necessary for people to do the basic reading on your own.
Anyway
> https://docs.microsoft.com/en-us/windows/wsl/about > The Windows Subsystem for Linux lets developers run a GNU/Linux environment -- including most command-line tools, utilities, and applications -- directly on Windows, unmodified, without the overhead of a virtual machine.
This is one of my top hits I see when I search for windows subsystem for linux. By default it isn't going to give you a GUI out of the box, it isn't a VM (not fully true with WSL2 anymore), so it isn't going to give you a desktop/gui. It just lets you run software.
Here's my opinionated solution which I setup in WSL a few days ago:
Use https, not ssh Use a GitHub access token Enable git-credential-store
https://git-scm.com/docs/git-credential-store
It'll store the access token in ~/.git-credentials. If that's a problem for personal security reasons, you can use the "cache" helper instead. It'll cache in RAM for a configurable period of time, default 15m.
https://help.github.com/articles/caching-your-github-password-in-git/
For remapping keys I use SharpKeys and Chocolately as a package manager (But it's not even close to pacman..).
Seriously though, why Windows instead of a linux distro?
Are you talking about in the terminal? I suggest you give WindowsTerminal a try. You can set settings like font size in the profiles.
Easiest way to install is via the Windows store.
For anyone looking for this: Heres the issue on the repo in case you want to track it: https://github.com/microsoft/terminal/issues/653
and heres a solution that a user posted as a workaround for now: https://github.com/rzym-on/termial-tray
WSL2 doesn't support network bridge mode yet, it's still NAT for now. So if you need to ping or scan your Wi-Fi from inside WSL2, you're SOL.
WSL2 also doesn't support full graphics either, but they announced they will fix that soon so that should not be a problem for much longer.
I use Windows Terminal with WSL2 and it's great. Once it gets graphics support for GUIs it will be awesome.
This is because ctrl+alt is supposed to be treated the same as AltGr on some keyboards. You might be able to find more info by searching the terminal repo for AltGr
I know this sounds ridiculous, but could this be the interaction of two bugs:
'\r'
sent by Windows Terminal, even though it's communicating with a *nix system.r
" somehow gets passed into the vim
instance, triggering replace?Maybe it's a regression associated with a previously solved CRLF bug. Like this one.
EDIT: Oh look, here is the exact bug.
For tabs I'm using ConEmu but there is also the new Microsoft Terminal which works really well.
However I've not used/know anything for replicated commands and split windows. It's worth having a look through the github issues for Terminal to see if they are considering your features and raise it yourself if necessary.
FYI, the acrylic options only work when you do not have an image set as the background. There is an issue open that will be fixed in an upcoming release. You can actually take a peek at the issues on git hub and open a new one for any of your other quibbles here: https://github.com/microsoft/terminal/issues
If you can repro, please file a bug on https://github.com/microsoft/terminal.
If you were sufficiently intrepid, you could even clone, build, and debug your own ConHost to find out if there's anything in Windows causing this issue, or if it is, in fact, Vim!
Ahhhh, the joys of open-source :)
No, Alacritty is the fastest terminal but that doesn't help WSL because the terminal itself is not the bottle-neck. It's just going to take MSFT some time to make the underlying technology faster. Or you have to buy a faster CPU/SSD
I installed it with these instructions: https://www.kali.org/docs/wsl/win-kex/
I had it work the 1st time I ran it then it failed the next time I restarted WSL2.
Someone here pointed out that it will not run under root which WSL uses after the first distro boot. I logged in as my regular id and win-kex worked. Now it doesn't work under either id but I found that win-kex is crashing:
Description
Faulting Application Path: \\wsl$\kali-linux\usr\lib\win-kex\win-kex
Problem signature
Problem Event Name: InPageError
Error Status Code: c000000d
Faulting Media Type: 00000000
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033
Additional Information 1: 2beb
Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46
Additional Information 3: 146e
Additional Information 4: 146e76a22a53215b6219e5ad140768df
​
Extra information about the problem
Bucket ID: d441e50e935bc62080a878d0822af8ea (659865)
update: i have managed to fix this by changing windows terminal profile commandline & startingdirectory to below values
​
"commandline": "wsl -d kali-linux kex wtstart",
"startingDirectory" : "//wsl$/kali-linux/home/"
​
if you follow the official win-kex guide from kali & got the same error as me simply change these values. ✌
For tilling manager, maybe it is worth taking a look at Microsoft PowerToys' FancyZones. It is actually a window manager, but I find it awesome.
Yes, but that way if you're running a docker command inside your WSL2 distro it will run across multiple OS's like this (WSL2 Main Distro <-> Windows <-> Docker WSL2 Backend). You will also lose the filesystem performance benefits of WSL2 when doing bind mounts or using volumes.
The only reason Docker for Windows with WSL2 backend exists is so you can run docker commands from Windows CLI. If you fully embrace WSL2 for everything then it is useless and will hurt your performance. This is even Docker's own advice.
I've been working on the exact same setup the last few evening, and I really enjoy it! This video could have been very useful beforehand. It will surely help other :)
If Docker is a must for you (like me). You can now enjoy it on your Windows Home machine, just enroll in the Windows Insider program and you can now use the Docker Desktop instead of Docker Toolbox and setup WSL2 in the easiest way ever! Here is some info from Docker:
https://www.docker.com/blog/docker-desktop-for-windows-home-is-here/.
Of course you can also just wait for this feature to be release "officially"!
Happy to help if there is any question!
> I personally don't use WSL for real projects because I don't think it's mature enough ... I think Docker would be your next best bet,
FWIW, the Docker team believe in WSL2 enough to bet on it entirely for Docker Desktop on Windows: https://www.docker.com/blog/new-docker-desktop-wsl2-backend/
FWIW, many, MANY people are using WSL for real, production Linux workloads every day.
If you do uncover issues with WSL/WSL2, please find/file an issue on the repo: https://github.com/microsoft/wsl.
With Docker Desktop, you can containerize Windows applications. That's what I mean by Windows containers.
You can safely ignore them for the moment and focus on learning docker inside the WSL2 environment. It will work exactly like it would inside a Linux VM, because WSL2 is a Linux VM that has been tightly integrated with Windows.
Sorry if this is slightly OT, but I tried out pretty much all launchers (that include start menu entries as I don't want to set everything up manually) and switched from launchy long ago (slight execution and search delay), I've finally settled on Keypirinha which is utterly amazing (and Open Source; kinda. I don't think it's OSI approved but very permissive) in both speed and features.
And while I'm posting anyway: What advantage does going wsl -> ssh give you over Powershell -> ssh?
Use a terminal that doesn't suck. I'm currently using cmder or the XFCE terminal. I know, that's a bit perverse, starting bash in a terminal, starting XFCE then using the XFCE terminal, but it works well. And it's better than trying to deal with the relic from the 90's the MS calls a terminal.
What do you mean with Android-Emulator? If you want to run Android programs on Ubuntu you can use Anbox.
If you want to a real emulator, what is wrong with the stock emulator from the android sdk?
yeah man also i wanted to have folder and files starting with dot to be hidden, so i opened the feature request here.
https://github.com/files-community/Files/issues/3055
i could never expect windows default to support this feature
On this page it says you need to use the browser alias (i.e. chrome:
), not path:
In most Linux systems eth0 is the first Ethernet adapter. It's probably trying to open with more privs than WSL can deliver right now.
For reference, the native Windows version of nmap requires winpcap to be installed.
Have you tried to setup it by yourself? After struggling for several hours I ended up being unable to mount synched folders because vagrant doesn't support it from a WSL2 filesystem: https://www.vagrantup.com/docs/other/wsl#synced-folders
How can it's possible to say that it "works" if you can't mount your files to VM? And files linked through DrvFS (/mnt/c/) on WSL2 are x30 times slower than on WSL1.
On the slightly heavier but super-portable side, take a look at vagrant
I know you said you didn't want VMs, but it makes it pretty damn easy to do VMs. There's also a docker provider, and probably other lightweight ones: https://www.vagrantup.com/docs/providers/
The best part is that the default VirtualBox provider it pretty damn portable across OSes.... you can test the same VMs across Linux distros, Windows, and OSX, and even cloud providers like AWS, OpenStack, DigitalOcean with relatively little fuss.
Once you have it installed, just go a directory and run
vagrant init
edit the Vagrantfile to choose the linux distro and other advanced options you want, it'll download them automatically for you.
vagrant up vagrant ssh
and you're in whatever OS you want out of the extensive library. It's meant to be cleanly rebuilt from scratch whenever you want, using the shell scripts or other provisioner frameworks like ansible or chef, but it's persistent until you do a
vagrant destroy
According to this page (https://www.vagrantup.com/docs/hyperv/boxes.html) when creating a base box you have to include additional drivers to make it compatible with hyperv, so if the creator of the base box that OP is using did not do this then they will not have success with just switching the provider to hyperv.
Haven't tried it, but it seems like you could convert a box from virtual box provider to hyper-v.
Of course if the box you were using was built with packer, and the packer files used for the box are available, it might be easier to just download the packer script adjust it to build a new hyper-v box.
If you want to use vim under Windows you can also just use vim.org binaries or if you want a somewhat compatible Linux wrapper, that performs faster than WSL, use msys
Running it through WSL means that there is a translation layer for working with windows native paths and tools, with WSL2 you have a virtual machine in between the regular files and windows files
Unfortunately not yet. I tried changing different settings in Symantec - didn't help.
As it works with the same Symantec with the same settings on the laptop of my colleague, I doubt, that the issue is in Symantec itself.
Did you have some VPN services installed? Like Cisco Any Connect or NordVPN. They change something in adapter configuration and it could be the reason. At least it is the last direction which I followed in my researches.
I also checked NAT rules - they are empty.
I tried to reset my Network adapters. Tried uninstalling both Cisco and NordVPN. Nothing have helped.