![High CPU usage (~100%) while not running any containers, host=MacOS, new issue in version=4.5.0 · Issue #6166 · docker/for-mac · GitHub High CPU usage (~100%) while not running any containers, host=MacOS, new issue in version=4.5.0 · Issue #6166 · docker/for-mac · GitHub](https://user-images.githubusercontent.com/1905093/162673694-3ec11dfa-530f-45c4-8a2e-2aab81ee2e6c.png)
High CPU usage (~100%) while not running any containers, host=MacOS, new issue in version=4.5.0 · Issue #6166 · docker/for-mac · GitHub
![mac osx - MacOS M1 - Docker desktop Why qemu-system-aarch64 takes large amount of memory once it starts? - Server Fault mac osx - MacOS M1 - Docker desktop Why qemu-system-aarch64 takes large amount of memory once it starts? - Server Fault](https://i.stack.imgur.com/jEsxR.jpg)
mac osx - MacOS M1 - Docker desktop Why qemu-system-aarch64 takes large amount of memory once it starts? - Server Fault
![Docker on macOS at native speed using Ubuntu Virtual Machine (both Intel and Apple Silicon CPU) | by Jan Mikeš | Carvago Development | Medium Docker on macOS at native speed using Ubuntu Virtual Machine (both Intel and Apple Silicon CPU) | by Jan Mikeš | Carvago Development | Medium](https://miro.medium.com/max/724/1*2XYLtY8BBC8T9CcnAnyZkA.png)
Docker on macOS at native speed using Ubuntu Virtual Machine (both Intel and Apple Silicon CPU) | by Jan Mikeš | Carvago Development | Medium
![High CPU usage (~100%) while not running any containers, host=MacOS, new issue in version=4.5.0 · Issue #6166 · docker/for-mac · GitHub High CPU usage (~100%) while not running any containers, host=MacOS, new issue in version=4.5.0 · Issue #6166 · docker/for-mac · GitHub](https://user-images.githubusercontent.com/58729567/155306994-2d59bd54-ba24-4b1f-9c15-2e4cc3cdc256.png)