4 ms·

I haven't had that experience myself, I can run Docker for Mac on my M2 Air without issues. Is your actual workload using 100% of the virtualized CPU?

monero-xmr 3y ago
Somehow it’s always at 100%, battery draining, laptop hot as hell. Quitting docker always solves it. It isn’t the workload. All devs have same issue. Maybe something with Postgres / redis containers (?)
- sundvor 3y ago
  Docker on WSL2 runs incredibly well. I love their Terminal as well, it's perfect for Ubuntu things. So yeah I'm on Windows, but I'm also on Linux. :D
  - osivertsson 3y ago
    I’ve been using the Moby packages from Microsoft in WSL2 and it works great. I followed https://gist.github.com/noelbundick/fa8a4ddec573b00f10f3b472ac2150df https://gist.github.com/noelbundick/fa8a4ddec573b00f10f3b472... No need for the commercial Docker parts that drain all performance.
    - sundvor 3y ago
      Oh thanks! I will check this out, cheers.
happymellon 3y ago
Ive not always had 100% CPU issues, but with multiple companies and various applications, Docker on Mac will use a lot of resources and cause fans to spin up which would never do so under any circumstance. It could be the terrible AV/"security software" conflicting with a VM, but the results are always the same. If we are just going to be using VS Code or IntelliJ and run Linux, what are we even using MacOS for? The terrible UI?
- monero-xmr 3y ago
  That’s a good point - we do have AV scan software which is mandated by SOC2 / ISO nonsense. Why Apple - the richest company on earth - is apparently so “bad” on security that we need 3rd-party malware app to “protect” us is a mystery.
  - ThomasBb 3y ago
    Your comment answers itself: it’s nothing inherent to macOS that needs AV scan - it’s the company policy, often driven by external compliance requirements and perhaps a lack of understanding - that leads to the outcome where multiple redundant AV mechanisms end up in your machine.
    - happymellon 3y ago
      Multi-AV was bad practice in the late 90's, why are we back here again? I don't know if the situation has changed but most of them used to tell us to not run multiple ones together.

monero-xmr 3y ago

Somehow it’s always at 100%, battery draining, laptop hot as hell. Quitting docker always solves it. It isn’t the workload. All devs have same issue. Maybe something with Postgres / redis containers (?)

sundvor 3y ago
Docker on WSL2 runs incredibly well. I love their Terminal as well, it's perfect for Ubuntu things. So yeah I'm on Windows, but I'm also on Linux. :D
- osivertsson 3y ago
  I’ve been using the Moby packages from Microsoft in WSL2 and it works great. I followed https://gist.github.com/noelbundick/fa8a4ddec573b00f10f3b472ac2150df https://gist.github.com/noelbundick/fa8a4ddec573b00f10f3b472... No need for the commercial Docker parts that drain all performance.
  - sundvor 3y ago
    Oh thanks! I will check this out, cheers.

happymellon 3y ago

Ive not always had 100% CPU issues, but with multiple companies and various applications, Docker on Mac will use a lot of resources and cause fans to spin up which would never do so under any circumstance. It could be the terrible AV/"security software" conflicting with a VM, but the results are always the same. If we are just going to be using VS Code or IntelliJ and run Linux, what are we even using MacOS for? The terrible UI?

monero-xmr 3y ago
That’s a good point - we do have AV scan software which is mandated by SOC2 / ISO nonsense. Why Apple - the richest company on earth - is apparently so “bad” on security that we need 3rd-party malware app to “protect” us is a mystery.
- ThomasBb 3y ago
  Your comment answers itself: it’s nothing inherent to macOS that needs AV scan - it’s the company policy, often driven by external compliance requirements and perhaps a lack of understanding - that leads to the outcome where multiple redundant AV mechanisms end up in your machine.
  - happymellon 3y ago
    Multi-AV was bad practice in the late 90's, why are we back here again? I don't know if the situation has changed but most of them used to tell us to not run multiple ones together.