3 ms·
> Try running a few docker containers to support development work. Docker containers should not take more memory than the same app running without docker + a f
by viraptor 10y ago
> Try running a few docker containers to support development work.
Docker containers should not take more memory than the same app running without docker + a few megs for duplicated libraries. What matters is what's running in the containers.
- cesarb 10y agoDoesn't Docker on Mac run the containers inside a Virtualbox VM running Linux? That should take quite a bit more memory than just running the app directly.
- viraptor 10y agoI'm comparing running on linux+docker vs running on linux. Virtualisation is present in both. If you've got the possibility to run the same app directly on OSX and you're not preparing for deployment on another system... why wouldn't you do that instead?
- bydo 10y agoDocker for Mac uses the built-in Hypervisor.framework through xhyve. Still virtualizating Linux, though, so there's some overhead.
- mhw 10y agoIt used to, but the newer Docker for Mac uses xhyve which is more lightweight. It also by default runs a pretty stripped down version of Linux. The default VM size is 2Gb, but you can increase that if you need to. I'm currently working on a project which involves a Docker replication of a production environment. The Docker Compose environment has 7 docker containers including Cassandra, Kafka and Flink plus some nodejs micro-services. This all runs happily in a 6Gb docker container leaving memory free for Eclipse, Atom, Outlook and a bunch of other applications on a 16Gb 2015 MacBook Pro. At no point have I felt that the machine is performing poorly due to memory exhaustion.