Probably people in Korea or even nProtect themselves.

That said, fixing a bug related to software incompatibility with Wine might also benefit other applications (since Wine may behave as “expected” as it runs on Windows). This is why they even tested Audacity to run on Wine even that a native Linux version is available.

Run any Linux (I recommend Debian) as a Hyper-V VM, give it a 4-8 gigs of ram, and put all your containers there as you would on an RPi.

Debian usually backports security fixes to older versions, so you may wanna check to Debian if they have an updated version of the package with the security fix.

This can be done by taking the CVE number related to this vulnerability and look at the package changelog.

There is even a tool to convert Docker Run commands to a Docker Compose file :)

Such as this one hosted by Opnxng:

https://it.opnxng.com/docker-run-to-docker-compose-converter

I think Cloudflare DNS works too and it’s free.

As most have pointed, the “always 2x” rule doesn’t have that much of relevance in 2023 as most computers now has more than 4GB of RAM. I would only use that much of a swap when using a low hardware.

For desktop, I would never go swapless, though. In the event of memory pressure, swap would still help in that situation so that OOM Killer do not kick off and unintentionally kill my working process. Plus it helps that Linux can move the least used data to the swap and use the RAM for filesystem cache.

So my rule of thumb, for desktop: If RAM < 8GB: Swap == 2x RAM If RAM => 8GB: Swap == 1x RAM

For servers, I think it depends on the workload. I keep a small amount, like probably 50% of RAM or less. But for stuff like Redis, it doesn’t make sense to have swap. You want to ensure that everything is in the memory.