WSL2 with Docker Desktop support #76
Replies: 4 comments
-
Great, thanks for the info! Does this give you the correct CPU usage and memory of the windows host as well? |
Beta Was this translation helpful? Give feedback.
-
Well, CPU name is reported correctly, so I assume yes, while for memory it says "total" 8GB, while I have 16 on the host. If I run
Not sure who/what allocated that mem to the VM, I don't remember having set anything up myself and this Debian guest was originally WSL1. |
Beta Was this translation helpful? Give feedback.
-
One thing that could be improved is disk space. It grabs "/" but in
|
Beta Was this translation helpful? Give feedback.
-
Also btop doesn't get disk info: |
Beta Was this translation helpful? Give feedback.
-
Hi,
I have a Debian WSL2 install on Windows 10 and I also installed Docker Desktop with WSL2 support.
Running
beszel-agent
in a terminal works fine using an external HUB (like on a VPS); the only requirement is to open the port on your router (port-forwarding), on Windows Firewall and last, but not least, on WSL itself:Open a CMD prompt with admin permissions and run:
netsh interface portproxy set v4tov4 listenport=45876 listenaddress=0.0.0.0 connectport=45876 connectaddress=<wsl2 IP>
to get
<wsl2 IP>
run:ip a
and look for `inet' on eth0inet 172.27.22.69/20 brd 172.27.31.255 scope global eth0
"172.27.22.69" in my case
If you have multiple VMs, chose the right one, obviously.
As for the filesystem, I ran:
df
and looked for "mounted on /"
Just to be clear, containers running in Docker Desktop are successfully shown in beszel stats.
I haven't tried running the agent in Docker, because it looked like over-complicating things.
Cheers
Beta Was this translation helpful? Give feedback.
All reactions