I think GP is specifically complaining about "Docker Desktop" (the GUI), not "Docker" (the service) itself. Here are some alternative GUIs for managing Docker: https://www.cloudbees.com/blog/docker-guis/
Otherwise, VMs are usually overlooked as an alternative to "docker images", most probably because many people entered the industry after docker images became popular, and they don't know anything else. If you design it properly, stick with establish technology like QEMU, you can have the same environment without having to touch docker at all.
VMs are great. I've been using them for work stuff since Hardware virtualisation made it practical to run VMs with little or no performance penalty.
That said, swapping from Docker to VMs for things is nowhere near as simple or straightforward.
The near-frictionless ability to stand up/tear-down a 'known' good image and configuration, with the ability to swap in/out networking, volume or other environmental configuration is what made Docker so popular.
We use Docker containers for a wide range of things, and while we could reproduce all of that as VMs - it would take a lot more effort, and it would introduce a lot more delays waiting to build/replace a VM.
> people entered the industry after docker images became popular
I don't think this is the only reason people use docker. Docker let's you compile an artifact and deterministically recreate that artifact at any point. When you want to deploy this artifact everything is hermetically included in it. No network access or startup time. Just starts and it's good.
If you have VM tooling that lets me do that without spawning a VM repeatedly and doesn't give me an effective way to modify the FS & copy my programs in (packer) then let me know. I haven't found anything VM related that's simple to use
In addition: vms still have a performance hit much more significant than processes.
For docker desktop you should be able to manage your own Linux VM install and forward the dockerd socket to your host machine and use the docker tooling with the appropriate DOCKER_HOST environment variable. As far as I remember, that's basically how docker desktop works.
Otherwise, VMs are usually overlooked as an alternative to "docker images", most probably because many people entered the industry after docker images became popular, and they don't know anything else. If you design it properly, stick with establish technology like QEMU, you can have the same environment without having to touch docker at all.