Folks, I have a node.js script running on my Windows machine that uses the dockerode npm package to talk to docker on said box and starts and kills docker containers.
However, after the containers have been killed off, docker still holds on to the memory that it blocked for those containers and this means downstream processes fail due to lack of RAM.
To counter this, I have powershell scripts to start docker desktop and to kill docker desktop.
All of this is a horrid experience.
On my Mac, I just use Colima with Portainer and couldn’t be happier.
I’ve explored some options to replace Docker Desktop and it seems Rancher Desktop is a drop-in replacement for Docker Desktop, including the docker remote API.
- Is this true? Is Rancher Desktop that good of a drop-in replacement?
- Does Rancher Desktop better manage RAM for containers that have been killed off? Or does it do the same thing as Docker Desktop and hold on to the RAM?
Are there other options which I’m not thinking of which might solve my problems? I’ve seen a few alternatives but haven’t tried them yet -
moby,
containerd,
podman
I don’t actually need the Docker Desktop interface. So pure CLI docker would also just work. How are you all running pure docker on Windows boxes?
At this point i would just install a linux distro like ubuntu/debian/arch as a VM on virtualbox/vmware/hyperv and do it from there, WSL2 is supposed to be custom ubuntu minus gui running on hypervany way.
WSL2 supports GUI apps.
Meant to say a guo DE, not sure you can run plasma/jde on that, maybe with vnc/rdp? But still its with x11 server iirc.
Why would you need a desktop environment though? You’re already running Windows. You can run individual Linux GUI apps, which is enough for pretty much all use cases.
WSL2 runs ubuntu on Hyper-V. It isn’t really as custom as you’d think. You can install other distros besides ubuntu. Or you can install regular ubuntu instead of LTS.
Take a look at this for running other distros: https://learn.microsoft.com/en-us/windows/wsl/use-custom-distro
It’s using Hyper-V technology, but it’s not just a VM, and can run on OSes that don’t run Hyper-V, like home editions. https://learn.microsoft.com/en-us/windows/wsl/faq
TIL, thanks.
And as such it’s perfectly suited for what OP is trying to achieve. A custom VM will be a lot more work than using WSL2.
I wouldnt say a lot, maybe its more, but i would estimate 15min for wsl2 vs 45min for virtual box. Plus you get lot more featues than plain wsl2 and its quirks.
WSL2 is already installed and running without any extra setup required, so all the setup time for the VM is additional time you have to spend. You’ll have to fiddle a lot longer than 45min the first time you set it up if you want parity with the WSL2 installation (bidirectional mounts, bidirectional network access, GUI applications as normal windows, integration into Terminal etc). Until everything is running you’ll probably spend half a day, since you’ll have to first look up how to best do these things for your VM environment. Even more so if you want to use Windows tools with WSL2 integration, like the whole IntelliJ suite.
What features and quirks are you referring to?
Is it pre installed nowadays? I rember having to go to some store and doing stuff to get it…
Mounts and networks should be just checkboxes, dropdowns iirc.
Terminals are probably better on linux anyway, if we really want the stone age windows tools we can always ssh into it from windows.
I didnt really get the gui part, linux vm can have, and run GUIs, all the intellij stuff are available for linux natively. Even then iirc they can run with any linux remotely as well, just needs ssh. If you need it to run on windows like native apps, maybe use Xserver via ssh.
As far as quirks I read some comments in this thread about filesystem being too slow, maybe there are more.
And now that i have typed all these, if you want it to look and feel exactly as windows withput any compromise, idk…
Wut? The Windows tools are a lot newer than the Linux ones. Windows Terminal is better than anything preinstalled on a Linux desktop IMO
What are some features that the new windows terminals have that linux terminals don’t?
It supports tabs out-of-the-box (not all the Linux ones do).
It supports profiles so you can have easy access to different commands/shells along with keyboard shortcuts to create a new tab using a specified profile:
Profiles aren’t just for the entire window - You can use a different profile per-tab (I think GNOME Terminal forces you to use the same profile for the entire window).
You can customize colours and fonts per profile. Has a nice font by default (Cascadia Mono).
It’s hardware-accelerated, so fast-scrolling text doesn’t lag.
Full UTF-8 and UTF-16 support.
Full accessibility (screen readers, etc) support.
Search.
Linux terminals may support all these features now… Which one do you use?
Thank you! I use whatever default terminal comes with Ubuntu, and it sucks.
It’s not pre-installed, but it’s checking one checkbox. Less work than deciding which VM provider to go with.
They should be, and yet I’ve rarely seen them work out like that. Usually I have to debug some issues and follow x StackOverflow responses which don’t work properly. Haven’t had any such issues with WSL2 yet.
… no. Windows Terminal integrates with WSL2 and allows you to open a terminal in Linux without having to set up anything inside of a good Terminal app in Windows. It’s what you’re asking for, but without any setup.
Yes, but inside of a separate canvas. WSL2 GUI apps run as normal windows.
Okay, but I’ve tried running them in a VM and in WSL2. It is integrated the best if you run it under Windows and use the native WSL2 integration. Everything else degrades the experience.
Yes, and then you have to set everything up. With WSL2 in PyCharm I select “Use WSL2 Python”, it lists all the WSL2 Pythons, and I select the WSL2 Python I want. Is it really so difficult to understand that there is a difference between being able to do something and something just being available without setup?
Or I install WSL2 and skip all that.
Yeah, you should read up on how WSL2 works. This is not an issue in any different way from VMs. WSL2 is a VM. It’s everything you’re asking for, but standardized, pre-installed and perfectly integrated. I don’t know why you’d recommend spending all those hours when it’s absolutely not necessary.
It’s like telling a beginner “Yeah, do Linux From Scratch, Ubuntu is way too convenient”.
Time to share this wisdom with IT security departments of the companies I worked for. Wsl2 is in the zero trust white papers of MS (or whatever IT security uses to take decisions). Real distros are not. Result, no trust…
Enterprise IT… Non sense since the 70s