3 ms·

Compare this with vagrant

evilduck 13y ago
Vagrant mostly just generates virtual machines (with the option of running a provisioner), so it would basically be the same comparison. Edit: I suppose you could be using Vagrant to provision VPSs and use your provisioning tool to deploy an app in one fell swoop, but most people don't reprovision a box every time they redeploy their software. Vagrant lets you build a base box, Docker is for deployment on top of that box.
- awongh 13y ago
  I also thought that another difference was that vagrant can also manage cpu-level (hypervisor?) VMs (as opposed to just linux containers) - one of the main use cases for vagrant would be running it on your local computer- a laptop running osx or windows for example. Correct me if I'm wrong, but you wouldn't be able to run docker on a windows laptop, b/c you're just containerizing the parent os.... I would be curious to see how this could run on osx.
  - evilduck 13y ago
    I've ran Docker on top of Linux, powered by a Vagrant VM just fine. It's exactly what their tutorial walks you through: http://docs.docker.io/en/latest/installation/vagrant/ http://docs.docker.io/en/latest/installation/vagrant/ I don't think OSX or Windows will run linux containers ever though. Maybe something conceptually similar, but I doubt it would be "Docker".
ams6110 13y ago
Since vagrant spins up full VMs, which need to boot, etc. it's slower. Spinning up VMs with vagrant, in my experience, takes tens of seconds to minutes. Launching an docker app in a container takes a few seconds (allegedly... I've never actually tried it myself).
- shykes 13y ago
  Actually the typical start time of a docker container is in the 10-100ms range :)
bryanlarsen 13y ago
If you have a Linux host, I highly recommend vagrant-lxc. This adds the speed/memory benefits of lxc/docker to the awesomeness that is docker. You don't have docker style provisioning/overlays, but that may be an advantage, especially if you already have provisioning scripts compatible with vagrant. To oversimplify: vagrant is for development, docker for deployment. But that's oversimplified, there's lots of overlap.

Vagrant mostly just generates virtual machines (with the option of running a provisioner), so it would basically be the same comparison. Edit: I suppose you could be using Vagrant to provision VPSs and use your provisioning tool to deploy an app in one fell swoop, but most people don't reprovision a box every time they redeploy their software. Vagrant lets you build a base box, Docker is for deployment on top of that box.

awongh 13y ago
I also thought that another difference was that vagrant can also manage cpu-level (hypervisor?) VMs (as opposed to just linux containers) - one of the main use cases for vagrant would be running it on your local computer- a laptop running osx or windows for example. Correct me if I'm wrong, but you wouldn't be able to run docker on a windows laptop, b/c you're just containerizing the parent os.... I would be curious to see how this could run on osx.
- evilduck 13y ago
  I've ran Docker on top of Linux, powered by a Vagrant VM just fine. It's exactly what their tutorial walks you through: http://docs.docker.io/en/latest/installation/vagrant/ http://docs.docker.io/en/latest/installation/vagrant/ I don't think OSX or Windows will run linux containers ever though. Maybe something conceptually similar, but I doubt it would be "Docker".

ams6110 13y ago

Since vagrant spins up full VMs, which need to boot, etc. it's slower. Spinning up VMs with vagrant, in my experience, takes tens of seconds to minutes. Launching an docker app in a container takes a few seconds (allegedly... I've never actually tried it myself).

shykes 13y ago
Actually the typical start time of a docker container is in the 10-100ms range :)

bryanlarsen 13y ago

If you have a Linux host, I highly recommend vagrant-lxc. This adds the speed/memory benefits of lxc/docker to the awesomeness that is docker. You don't have docker style provisioning/overlays, but that may be an advantage, especially if you already have provisioning scripts compatible with vagrant. To oversimplify: vagrant is for development, docker for deployment. But that's oversimplified, there's lots of overlap.