4 ms·
> BUT... you're recommending this as a workaround for limitations in expensive "Pro" local development machines, as part of an encouragement to go ahead and buy
by tshaddox 6y ago
> BUT... you're recommending this as a workaround for limitations in expensive "Pro" local development machines, as part of an encouragement to go ahead and buy them.
I agree with that in principle, but in practice Docker development on Intel MacOS already performs so poorly that it’s effectively broken anyway. I’ve actually been looking forward to Apple Silicon in the hopes that Docker starts over again and gets things working without the constant CPU pegging and 5-10x performance penalty.
- rootusrootus 6y ago> 5-10x performance penalty. I don't use Docker on Mac, but I'm curious how much of the performance penalty is attributable to VirtualBox. I use a VirtualBox-based Vagrant environment, and the performance is awful. It mostly comes down to terrible disk performance due to how VBox shares directories from inside the VM to the host filesystem. Apparently it can be fixed entirely by switching to local NFS, but I haven't had any success getting that working.
- closeparen 6y agoDocker for Mac uses a native hypervisor framework now, VirtualBox is not involved.
- PopsiclePete 6y agoI’ve been using docked on macOS for the past 5 years and it’s been quite pleasant. I had a few times when CPU was spiking and that was fixed with subsequent patches. Definitely over a year ago. I don’t think “constant CPU pegging” is a typical docker-on-Mac experience?