Since you mention executing the same files (with proper performance) from within Git Bash, I’m going to make an assumption here. Correct me if I’m wrong on this, and I’ll delete the answer and look for another possibility. This would be explained (and expected) if your files are stored on /mnt/c (a.k.a. C:, or /C … Read more
In case anyone finds this via search and doesn’t notice that there is actually a solution listed in the question, you can fix WSL clock drift via. sudo hwclock -s If you just need to do it occasionally, this is a fine solution. If you need to do it more frequently, consider @piouson’s solution
The generated file /etc/resolv.conf is: nameserver 172.24.0.1 ..had to change it to nameserver 8.8.8.8 which resolves the problem
This comes from the “vmmem” which consumes as much resource as it can. To solve the problem just go to your user file for me in C:\Users\userName In this directory create a file named “.wslconfig” in which you will configure how many resources can consume WSL2: [wsl2] memory=900MB #Limits VM memory in WSL 2 to … Read more
TL;DR: Add the following to your ~/.bashrc: export DISPLAY=$(ip route list default | awk ‘{print $3}’):0 export LIBGL_ALWAYS_INDIRECT=1 Enable Public Access on your X11 server for Windows.* Add a separate inbound rule for TCP port 6000 to the windows firewall in order to allow WSL access to the X server, as described by the wsl-windows-toolbar-launcher … Read more
The WSL 2 docker-desktop-data vm disk image would normally reside in: %USERPROFILE%\AppData\Local\Docker\wsl\data\ext4.vhdx Follow the following to relocate it to other drive/directory, with all existing docker data preserved (tested against Docker Desktop 2.3.0.4 (46911), and continued to work after updating the 3.1.0 (51484)): First, shut down your docker desktop by right click on the Docker Desktop … Read more