[tjscott]

The Docker daemon (likely the HyperKit VM) on the Mac has a tendency to burn CPU cycles, even when there are no containers running. It's pretty common for it to sit at 10-20% of a core all day, and sometimes gets pegged at 100% until you quit.

There are countless closed issues in the GitHub issue tracker [1] for similar issues, but the symptoms don't seem to go away for me or many of my colleagues.

It's been a pretty awful experience on Mac for a long time, so any competition is surely welcome.

[1] https://github.com/docker/for-mac/issues/3499

[laurencerowe]

I had the same frustrations until the other day I saw a tip to enable 'Use the new Virtualization framework' under Preferences -> Experimental Features. Since then Docker's background CPU usage has dropped to 1% and I no longer bother stopping it when I'm not using it.

[solarkraft]

My hopes for this were high, but it just makes my containers crash (until then networking works and it may be faster) on M1/Monterey.

[laurencerowe]

That’s probably why it’s still marked experimental! Works well for me on an M1 Mac running Debian/Ubuntu Arm containers.

[lugged]

Wow, Mac users put up with some bullshit to avoid configuration and have things "just [sometimes, unless you're holding it wrong] work"

[q-rews]

I'm happy your platform of choice has no bugs nor quirks. Could you let us know which one it is? We can probably help you find the bullshit you put up with that has become second nature.

[lugged]

I'm not the one claiming my system is the perfect dev machine.

[q-rews]

Plenty of Apple users complain about Apple, don’t just focus on the fanboys, which every platform has, even Windows.