Hacker News Reader

Comment by pxc | Hacker News Reader

Yeah there seems to be a memory leak in Hyper-V somewhere. Spinning up Docker containers on-demand (like for a local GitHub runner, for example) instantly gobbles up the whole allotment and, on defaults, makes my 32GB work computer totally unusable.

I really wish I could just run proper Linux on the metal. Docker under emulation is such a disaster! I don't understand how it's the norm.

View on HN

Whenever I’ve wanted to run Docker on a Windows machine I just install Linux under virtualization and then install Docker under Linux. It works, which is more than I can say for the alternatives.

I know some people think WSL2 is the bee’s knees but I just tried to install it on a brand new ‘gaming computer’ with 64MB RAM and Windows 11 and… it didn’t work at all.

WSL2 is the only VM I can run at work without seeking some kind of special permission, unfortunately.

It's quite possible that a normal distro under some other hypervisor would work much better for me.

> 64MB RAM and Windows 11 and… it didn’t work at all

Not too surprising to be honest

It's weird.

I know people who swear WSL2 was an improvement over WSL1 but I'd say WSL1 worked 100% of the time when I tried it and I've never had WSL2 work correctly. Contrast that to booting up a VM in Hyper-V where it might take me two tries to make a perfect install.

I swear it's improvement. Switched from wsl1 long time ago - 3 or 4 years I guess. Using Wsl1 for very specific task of doing socket forwarding from host OS, the rest happens in WSL2. Simple thing like using namespaces or not so simple like mounting loopback file with BTRFS not possible in WSL1 by design. Not even mentioning recent systemd support.

I think they were refering to the "64MB" typo

I've read a github thread about the issue the maintainer said that a change should be made in the linux kernel itself.

Reply on news.ycombinator.com