*resending this as it failed to post to the group* My knowledge of Docker is a bit limited so I'm going to try to avoid mudding the waters around this topic more, but I just wanted to add my 2 cents as I find this analogy a bit lacking.
> VirtualBox -> Docker > Vagrant -> unknown tool Both Vagrant and Docker are complex tools and I think there's more beneath the surface than that. To me the analogy looks more like this: VirtualBox -> LXC Vagrant Boxes -> Docker Images Vagrantfile -> Dockerfile The Dockerfile allows you to specify a base image to use, then additional shell commands to run (e.g. apt-get install mysql) used to build your custom image. If you wanted to distribute just the Dockerfile in the repo and let everyone build the image locally then it would work very similar to Vagrant. Docker also easily allows you to distribute the built image. Vagrant also allows this with it's boxes (either through `vagrant box repackage` or with packer). On Tue, Aug 19, 2014 at 10:25:50AM -0600, Lonnie Olson wrote: > On Tue, Aug 19, 2014 at 9:19 AM, Tod Hansmann <[email protected]> > wrote: > > We inherited some external projects at digEcor that did use it in > > production, and we had to stop that. For a while though, that was the way > > to get a production system out of that code monstrosity. > > No one has recommended Vagrant for production use. Only development use. > > Vagrant is a method to automate the creation of a development > environment that mirrors the production environment. Since your > development environment should match your production environment as > closely as reasonably possible, Vagrant is an amazing tool for > matching a production environment that utilizes full machines or > virtual machines. If you use Docker in production, then utilizing > Docker for development would be recommended. > > I agree with Richard regarding the idea that passing around a > Vagrantfile is better than passing around a binary blob Docker > container. A Vagrantfile and it's supporting infrastructure (Puppet, > Chef, Salt) can be put into version control easily. > > But I also think that the comparison is faulty from the start, apples > and oranges and such. > * Vagrant is a tool for automating the building of dev environments. > Docker is *not*. > * Docker is a lightweight virtualization tool. Vagrant is *not*. > > VirtualBox -> Docker > Vagrant -> unknown tool > > I think someone needs to create a tool, or perhaps extend Vagrant, to > create Docker containers. > > _______________________________________________ > > UPHPU mailing list > [email protected] > http://uphpu.org/mailman/listinfo/uphpu > IRC: #uphpu on irc.freenode.net ----- End forwarded message ----- _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
