news.ycombinator.com
Docker for Desktop went from being complete garbage to a ...
Excerpt
1. We were all spending 6-8 hours per week trying bending our host OS to work like Linux. Containers, package managers, compatibility layers, different autocompletes, etc... all do create work. All the adaptations to avoid running Linux also often don't work identically to the real thing (i.e. VM CPU & memory allocation vs. Linux container CPU & memory allocation, installing Postgres on MacOS vs Linux) so there's lots of little learning curves. … KronisLV on June 6, 2022 This is probably the most important point and something that I can wholeheartedly agree with! On Windows, you get the occasional issues with bind mounts or file permissions (e.g. wanting to use a container that has SSH keys in it, but software complaining about 77X access, instead of 700, which you literally cannot change), or even networking. … Running boring plain vanilla Ubuntu LTS with the ("curse you, FreeDesktop.org!") Gnome Shell and a few extensions that probably drive the minimalists on the Gnome Project bonkers (also running a lot of web apps like Gmail and Keep as PWAs). Or at least I hope they do.
Related Pain Points
Docker Desktop networking conflicts on Windows and macOS
7Docker Desktop's networking implementation interferes with other host applications like OpenVPN and Xbox Game Center on Windows and macOS. The volume and file permissions model on Windows is problematic, and Windows updates frequently conflict with Docker Desktop, causing runtime failures.
Docker Desktop Performance Degradation on Windows and macOS
6Docker Desktop emulates Linux containers using virtual machines on Windows and macOS, resulting in slow performance, excessive CPU consumption, and battery drain during heavy builds and container orchestration. Native Linux performance is significantly better, creating cross-platform friction.