WSL2 was promised as a good working extension for a Linux dev environment on windows by my peers. Sadly, a whole host of issues specific to my dev environment meant that it was useless as I’d spend more time fixing it than getting any valuable use out of it. More importantly, this became the very reason I switched to arch full time, and haven’t looked back since. I still hope that it becomes what it was promised to b…
Agreed, I can't use virtualbox and WSL2 at the same time, epic fail.
WSL2 corrupting Git repositories and shell history
281–290 of 423 posts
Re: WSL2 corrupting Git repositories and shell history
#282Re: WSL2 corrupting Git repositories and shell history
#283Earlier quoted context omitted.
This is probably HyperV. I’ve seen exactly this ext4 corruption in production on windows server 2012R2 with CentOS 7. Even to the point that the machine remounts root read only. Unfortunately our windows operations guys are severely lacking in diagnostic savvy and just reboot the machine over and over again or blast it and provision a new one and don’t analyse the problem. From what I’ve seen it’s a combination of th…
After upgrading to WSL2, I started having issues with a Virtualbox VM. Turns out it didn't play nicely with HyperV. I went back to WSL1.
Re: WSL2 corrupting Git repositories and shell history
#284Earlier quoted context omitted.
Opposite anecdata - I got a gaming PC and i migrated all my development to it and WSL(2) has been a godsend. VS Code has a "WSL Remote" mode that works really well (where a vscode server runs in Linux and the windows GUI access it "remotely"). I even use the Windows Github app for the occasional GUI-assisted commit, and apart from being slow its fine. I've had only two problems with this set up: - Occasionally VS Cod…
Also opposite anecdote, I switched from Pop!_OS to Windows after getting into music production recently as a hobby (MIDI controller driver software doesn't always play well, even with WINE-devel) after over a decade on Linux. I expected to hate it, but I'm asking myself why I didn't do this sooner. It's the same sort of scenario as before -- I have Windows running the games I occasionally play, and music stuff, and I…
Re: WSL2 corrupting Git repositories and shell history
#285Earlier quoted context omitted.
Agreed, I can't use virtualbox and WSL2 at the same time, epic fail.
Can you expound on this? Windows doesn't let you use VirtualBox and WSL2 at the same time?
Re: WSL2 corrupting Git repositories and shell history
#286More: - WSL2 sometime corrupt .zsh_history and git https://github.com/microsoft/WSL/issues/5026 - WSL2 corrupts ext4 filesystem https://github.com/microsoft/WSL/issues/5895
This is probably HyperV. I’ve seen exactly this ext4 corruption in production on windows server 2012R2 with CentOS 7. Even to the point that the machine remounts root read only. Unfortunately our windows operations guys are severely lacking in diagnostic savvy and just reboot the machine over and over again or blast it and provision a new one and don’t analyse the problem. From what I’ve seen it’s a combination of th…
Re: WSL2 corrupting Git repositories and shell history
#287Earlier quoted context omitted.
Opposite anecdata - I got a gaming PC and i migrated all my development to it and WSL(2) has been a godsend. VS Code has a "WSL Remote" mode that works really well (where a vscode server runs in Linux and the windows GUI access it "remotely"). I even use the Windows Github app for the occasional GUI-assisted commit, and apart from being slow its fine. I've had only two problems with this set up: - Occasionally VS Cod…
Also opposite anecdote, I switched from Pop!_OS to Windows after getting into music production recently as a hobby (MIDI controller driver software doesn't always play well, even with WINE-devel) after over a decade on Linux. I expected to hate it, but I'm asking myself why I didn't do this sooner. It's the same sort of scenario as before -- I have Windows running the games I occasionally play, and music stuff, and I…
Re: WSL2 corrupting Git repositories and shell history
#288Earlier quoted context omitted.
Opposite anecdata - I got a gaming PC and i migrated all my development to it and WSL(2) has been a godsend. VS Code has a "WSL Remote" mode that works really well (where a vscode server runs in Linux and the windows GUI access it "remotely"). I even use the Windows Github app for the occasional GUI-assisted commit, and apart from being slow its fine. I've had only two problems with this set up: - Occasionally VS Cod…
Oh you need to fucking disable Window's Defender though, or add exclusions for your Linux distro/WSL2 folder, because when installing "node_modules" it will attempt to do realtime scans for threat-protection which absolutely cripples the speed. https://www.cicoria.com/improving-windows-subsystem-for-linu... https://www.reddit.com/r/bashonubuntuonwindows/comments/eok7... "I noticed a significant performance difference…
https://docs.microsoft.com/en-us/windows/wsl/wsl2-mount-disk
Currently, the mount is not automatic so you can make a startup.ps script and run it on start through group policy.
Re: WSL2 corrupting Git repositories and shell history
#289Earlier quoted context omitted.
Also opposite anecdote, I switched from Pop!_OS to Windows after getting into music production recently as a hobby (MIDI controller driver software doesn't always play well, even with WINE-devel) after over a decade on Linux. I expected to hate it, but I'm asking myself why I didn't do this sooner. It's the same sort of scenario as before -- I have Windows running the games I occasionally play, and music stuff, and I…
I’ve always solved this issue by keeping windows on one drive and linux on another. It does have an upfront cost, but keeping my dev work / linux environment setup has always worked well for me. Lately I’ve thought of trying WSL, but I don’t see any real benefit over my current setup
Re: WSL2 corrupting Git repositories and shell history
#290Earlier quoted context omitted.
Can you expound on this? Windows doesn't let you use VirtualBox and WSL2 at the same time?
WSL2 uses hyper-v. You can only run either hyper-v or ESXi (VB's hypervisor) at the same time.