3 ms·
I made a mistake of purchasing a 8GB M1 MacBook Pro. It was painful to work with. For casual stuff it worked just fine, but as soon as I ran a Docker image (wit
by M4v3R 4y ago
I made a mistake of purchasing a 8GB M1 MacBook Pro. It was painful to work with. For casual stuff it worked just fine, but as soon as I ran a Docker image (with 2GB memory limit), had Slack and few other light apps open, some tabs in Safari it started to become slow. Painfully slow. The spinning beach ball was a very frequent sight to me. My RAM usage was often in the red zone and I had to kill applications constantly. When I finally bit the bullet and upgraded to a M1 Pro with 32 GB of RAM all of these issues went away.
- nicoburns 4y agoDocker on Mac is a pretty terrible experience in general in my experience. Better to run things natively if you can.
- vetinari 4y agoDocker on Mac (and Windows) is a full-blown VM. The containers assume Linux, so they are getting it -- inside that VM. That also brings issue with networking. Sure, if you are using the bridged (in Docker's parlance) networks, you won't notice. If you need to use host/ipvlan/macvlan, you will.
- astrange 4y agoVMs are much more memory intensive than other workloads because they wire a lot of memory and/or just access it constantly, which defeats pretty much every optimization you could conceivably do to hide it.