why are people not using Docker as compared to Vagrant ? Doesnt it consume way less memory ?
Automating Development Environments with Vagrant and Puppet
31–36 of 36 posts
Re: Automating Development Environments with Vagrant and Puppet
#32why are people not using Docker as compared to Vagrant ? Doesnt it consume way less memory ?
The nice thing about Vagrant is that it is more platform independent, so even if you are doing your dev work on a mac you can still use the same dev-box as anyone else. Docker, on the other hand, is linux only (and requires a certain kernel version) to work well. Not to say you can't use Docker, and they seem to work well together, but they are kind of solving different problems.
Re: Automating Development Environments with Vagrant and Puppet
#33why are people not using Docker as compared to Vagrant ? Doesnt it consume way less memory ?
How do you share files between the docker instance and the host? How do you run docker on your mac? Networking is very different for docker instances as well.
On a Mac you can use Vagrant to bring up a host that runs docker, but i'm not sure how you would be able to just run docker on your mac.
That being said docker looks pretty awesome for certain sets of problems.
Re: Automating Development Environments with Vagrant and Puppet
#34The limitation with this type of approach is the assumption of a conventional (and, some would say, out of date) architecture, ie. single service on a single VM on a single cloud provider. Topology specification, firewalling, resource constraints (bandwidth, IO speed/resilience... ie. RAID/backup persistence safety), service cohabitation or codependence, performance/capacity testing, cost, cloud provider abstraction,…
> ie. single service on a single VM on a single cloud provider. Vagrant allows you to specify groups of VMs that spin up together. Your general point that it doesn't simulate production perfectly is correct. But this is one case where the perfect is the enemy of the good.
Apparently to simulate production to the level OP requires, the only solution is to have the users test your product--the only way to perfectly simulate reality is reality.
Re: Automating Development Environments with Vagrant and Puppet
#35why are people not using Docker as compared to Vagrant ? Doesnt it consume way less memory ?
can docker have different operating systems with different kernels (win, freebsd, debian lin, ubuntu) running on the same machine? or same o/s with different kernels? different modules?
the old vps vs. container discussion.
Re: Automating Development Environments with Vagrant and Puppet
#36why are people not using Docker as compared to Vagrant ? Doesnt it consume way less memory ?
can docker have different operating systems with different kernels (win, freebsd, debian lin, ubuntu) running on the same machine? or same o/s with different kernels? different modules? the old vps vs. container discussion.
It is possible to run a VM inside Docker and still retain some advantages of containers, but not all of them since there is a "VM" in the sentence :)