for-win

Fifth thing: Bricker of Windows https://github.com/docker/for-win/issues/1549 Still pissed my HP Windows laptop was bricked from it a few months ago. I’ll never use it for anything.

I use containers on Mac and Windows for development (and we deploy on linux). Docker for Mac is _unusably_ slow in my experience. The VM that it runs is a giant resource hog and a battery hog, and doesn't support ipv6 [0] Docker Desktop itself is (another) resource hog, wildly buggy, and painfully slow. It's the epitome of "shitty electron app". On windows, docker desktop has all of the same issues as it does on mac. Docker's concept of volumes and file permissions on windows are nonsense. Windows updates and Docker Desktop regularly decide to disagree, [1] It's networking support interferes with other applications (like OpenVPN and the Xbox Game Center) [2]. [0] https://github.com/docker/for-mac/issues/1432 [1] https://github.com/docker/for-win/issues/599 [2] https://github.com/docker/for-win/issues/1976

> FWIW, when denying the request to wootric, the docker daemon crashes. A yes, this about fits the standard of engineering I've come to expect from Docker. Anyway, I couldn't find any references too "woocentric" anywhere in the code; looks like this part isn't open source? I did find this other issue: https://github.com/docker/for-win/issues/12718 with a comment from May 2022: "At some point we found out that bugsnag was actually sending a «session creation» request of some sort when initialized, even if no crash was actually being reported. We believed we had fixed that, but I just checked with a MITM proxy and it appears to have regressed… There may be some other services doing something similar without us realizing (wootric, …). We have created a ticket in our internal backlog to review all this."

> Both services support adding non platform games through their shortcut/executable. That only launches the game through the correct store. If the game doesn't implement cross play, you can't play together. > They also support voice chat for groups and players not in game. But you're trying to be in game with the person, and again if the game doesn't do in-game voice chat, you have to find alternatives. On a console you join a party and the software correctly handles the cases around "do I want to put you in a voice chat channel for your game" (because it has to to pass certification). > File a bug report? Or you just came up with some hypothetical issues? Really helpfully closed after 30 days of inactivity. https://github.com/docker/for-win/issues/42. (I didn't make this bug, but I found it, and just logged onto my xbox instead).

This has little or nothing to do with "podman people". The stuff people are talking about in the top comments have everything to do with people (and corporations) trying to figure out how to run podman efficiently on MacOS. It certainly can be done by bundling QEMU or through a VM. Second, Docker Desktop for MacOS and Windows are not open source, hence this repository is empty: https://github.com/docker/for-win

On the interwebs it says that Hyper-V is supposed to support memory ballooning (since about Windows Server 2012), just like other virtualization platforms. Maybe the Docker software just didn't use it, or maybe it requires a Windows Server license? edit: seems Docker just chose to disable it because they thought it made memory usage unpredictable: https://github.com/docker/for-win/issues/521

Amusingly, one of the linked issues from that one notes that a third piece of software made the same mistake - "Thunderbolt software by Intel" ( https://github.com/docker/for-win/issues/1301#issuecomment-3... )

This has been fixed in 2018!!! Why is this here? https://github.com/docker/for-win/issues/1723

Docker for Windows has had a fundamental Dns[1] bug since April of last year, I've been forced to run v2.0.0.3 for months now to ensure yum repos resolve inside AmazonLinux containers. Truly a second class platform. [1]: https://github.com/docker/for-win/issues/3810

Yea me too finally. Switched from running in vagrant today and it shouldn't have felt like an achievement. It should work in cygwin and ubuntu for windows sanely, but it doesn't and it's pretty slow and temperamental so I'm not sure how many re-installs or restarts will be required tomorrow. We had issues with our redis dataset being too large for the default memory allocation settings. Here's a relevant ticket if it's running slowly for you you might get some pointers: https://github.com/docker/for-win/issues/1936

Regarding 1), Docker implemented a cached volume mount option to mitigate the performance issues on MacOS [1], but last time I tried it, file system events stopped working. I'm not sure if this is an inherent limitation or if it's something specific to my environment. I'd appreciate if someone more knowledgeable could clarify. As for Windows, it doesn't have the same fs performance issues on volume mounts, but AFAIK file system events have never worked there [2]. My current reluctant compromise to make volume mounts work seamlessly across platforms is to use polling instead of relying on file system events. That way I can turn on caching on Docker for Mac, and everything just works. The downside is of course polling is inefficient, but I've found when you take care to exclude all non-source directories from the polling, it's usually not a

(I work at Docker) If you haven't already and can spare the time, could you file a pair of issues: perhaps one for the shared volume problem and another for the networking on https://github.com/docker/for-win ? We've been fixing bugs in both areas and the fixes should arrive in the beta channel over the next few updates. Thanks for your patience!