3 ms·

Docker is hopelessly broken on the Intel Macs, and from what I’ve heard it’s certainly not any worse on the M1 Macs.

masklinn 5y ago
> it’s certainly not any worse on the M1 Macs. Probably not any better either. If you want to run docker on a mac you probably should not, but the second best strategy is probably to bite the bullet and run an actual VM in which you do your docker stuff. Odds are a proper and well maintained hypervisor you keep running will be a lot better than whatever DfM does.
- tshaddox 5y ago
  > Probably not any better either. Probably, although you probably do still get better thermals and battery life with the M1 Macs.
dzhiurgis 5y ago
> not any worse About 6x worse perf in my specific case.
- tshaddox 5y ago
  Fair enough. My Intel Mac gets about a 5x performance penalty doing Webpack builds in Docker versus natively. My coworkers using M1 Macs report similar numbers. What workflows are you seeing M1 Macs getting 6x worse Docker performance than Intel Macs?
  - dzhiurgis 5y ago
    sort of explained here https://news.ycombinator.com/item?id=29144096 https://news.ycombinator.com/item?id=29144096
filmgirlcw 5y ago
Eh, it is worse. Worse to the point that even though I just got a MaxBook, I won’t even conceive of getting rid of my 2020 maxed out Intel iMac. And it’s why I have other x86 machines too for Linux or whatever, because containers on macOS are rough but containers and Docker specifically on the M1 is really rough. It is clearly an ecosystem/use case that Apple doesn’t prioritize. It makes the case for stuff like GiHub Codespaces or sshing into a remote machine via VS Code a lot more manageable. For everything else, the M1 is a beast, and even emulated, you can get a really good Linux experience (Windows too for that matter — games, obviously not withstanding), but containers? Nah. It’s worse than the already sad state on Intel Macs.

> it’s certainly not any worse on the M1 Macs. Probably not any better either. If you want to run docker on a mac you probably should not, but the second best strategy is probably to bite the bullet and run an actual VM in which you do your docker stuff. Odds are a proper and well maintained hypervisor you keep running will be a lot better than whatever DfM does.

tshaddox 5y ago
> Probably not any better either. Probably, although you probably do still get better thermals and battery life with the M1 Macs.

dzhiurgis 5y ago

> not any worse About 6x worse perf in my specific case.

tshaddox 5y ago
Fair enough. My Intel Mac gets about a 5x performance penalty doing Webpack builds in Docker versus natively. My coworkers using M1 Macs report similar numbers. What workflows are you seeing M1 Macs getting 6x worse Docker performance than Intel Macs?
- dzhiurgis 5y ago
  sort of explained here https://news.ycombinator.com/item?id=29144096 https://news.ycombinator.com/item?id=29144096

filmgirlcw 5y ago

Eh, it is worse. Worse to the point that even though I just got a MaxBook, I won’t even conceive of getting rid of my 2020 maxed out Intel iMac. And it’s why I have other x86 machines too for Linux or whatever, because containers on macOS are rough but containers and Docker specifically on the M1 is really rough. It is clearly an ecosystem/use case that Apple doesn’t prioritize. It makes the case for stuff like GiHub Codespaces or sshing into a remote machine via VS Code a lot more manageable. For everything else, the M1 is a beast, and even emulated, you can get a really good Linux experience (Windows too for that matter — games, obviously not withstanding), but containers? Nah. It’s worse than the already sad state on Intel Macs.