for-mac VS WSL

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

version: '3' services: graph-node: image: graphprotocol/graph-node ports: - '8000:8000' - '8001:8001' - '8020:8020' - '8030:8030' - '8040:8040' depends_on: - ipfs - postgres extra_hosts: - host.docker.internal:host-gateway environment: postgres_host: postgres postgres_user: graph-node postgres_pass: let-me-in postgres_db: graph-node ipfs: 'ipfs:5001' matic: 'matic:http://localhost:8545/' GRAPH_LOG: info ipfs: image: ipfs/go-ipfs:v0.10.0 ports: - '5001:5001' volumes: - ./data/ipfs:/data/ipfs postgres: image: postgres ports: - '5432:5432' command: [ "postgres", "-cshared_preload_libraries=pg_stat_statements" ] environment: POSTGRES_USER: graph-node POSTGRES_PASSWORD: let-me-in POSTGRES_DB: graph-node # FIXME: remove this env. var. which we shouldn't need. Introduced by # , maybe as a # workaround for https://github.com/docker/for-mac/issues/6270? PGDATA: "/var/lib/postgresql/data" POSTGRES_INITDB_ARGS: "-E UTF8 --locale=C" volumes: - ./data/postgres:/var/lib/postgresql/data

This bug has been around years and still not fixed as far as I know - see https://github.com/docker/for-mac/issues/3926

You're not wrong, and not the first to raise this https://github.com/docker/for-mac/issues/6061

https://github.com/docker/for-mac/issues/6867 This github issue might help. What worked for me was deleting the ~/.docker/buildx folder

There has been an outstanding bug [Docker Github] for years with the Docker team who do not seem to be able (or want to) address this - they have closed more than one issue but its still there.. The latest bug report is this one [Docker Github] but I honestly would not bother following it - no idea why they are not fixing this.

Have you checked if any of your other Docker containers become unresponsive at the same time? If so, it could be Docker. I had this issue on Docker for months until they finally came out with an update that works for me (Docker Desktop 4.19.0 for Mac).

It might have something to do with Docker? I was having issues a few months ago with all my containers becoming unreachable or very slow many times per day. I finally upgraded to Docker Desktop 4.19.0 (I’m on a Mac) and everything resolved. There were a few GitHub issues about it, too. You could try running a speedtest within different Docker containers and seeing if there’s a discrepancy. You could also check your RAM and CPU usage for different containers using something like Glances; it could lead to a clue.

It absolutely 100% can be true.

As an example: Windows Services for Linux 2 used a special init daemon to interact with the host OS.

That meant no systemd. That meant that the `systemctl` program wasn't there.

This baffled legions, armies, of wannabe sysadmins.

https://stackoverflow.com/questions/55579342/why-systemd-is-...

https://superuser.com/questions/1785697/systemd-in-wsl-on-wi...

https://github.com/microsoft/WSL/issues/9477

https://askubuntu.com/questions/1132230/unable-to-run-any-sy...

People on the whole have no idea how this stuff works, and they just copy magic incantations from StackOverflow to get stuff to happen. If that doesn't work, then this OS is broken. The end.

For these guys, WSL was broken.

Result:

MS hired Lennart Poettering.

https://www.theregister.com/2022/07/07/lennart_poettering_re...

He "fixed" it. Systemd now works in WSL2. All those guides for noobs now work. Everyone is happy.

In a world where tools like Flatpak and Snap are proliferating and it's driving deep divisions between Linux distros, if you think the average person struggling with Linux is going to use `ldd` to work out where the dependencies for something live, I'm afraid you are a deep guru who lives on a different plane of existence.

We now have widely-used packaging systems which simply embed an apps entire dependency tree into a package to avoid people having to work out the difference between `apt` and `rpm`. Thousands of terabytes of disk are being burned to make this stuff go away.

Yes, this is too hard. Way too hard.

Better source: https://github.com/Microsoft/WSL/issues/873#issuecomment-425...

One of the bugs where on the Docker side. As I have said, there have been several since release with a lot of impact period overlap. The latest and greatest is not resolved.

It's the issue of abysmal I/O performance in communication between the mounted WSL2 virtual hard disk and Windows mounts inside the WSL2 distro.

I found this github page and I was able to reproduce this from the answer

* Docker engine and not Docker Desktop in a VM. WSL2 works well after some configuration: https://github.com/microsoft/WSL/issues/6655#issuecomment-11...

Seems to more of a Defender issue than a WSL one, see https://github.com/microsoft/WSL/issues/8995

After adding exclusions for the fsnotifier-wsl process and and both variants of the WSL distro path my disk performance was improved.

Adding the idea64.exe process also helped since I was trying to run IntelliJ against projects inside WSL.