[cosarara97]

Vagrant gives you a full VM with a traditional init system. Docker is usually used without an init (or a very dumb init), so you'll have different containers for each service. It's a very different way of working, and I'd argue vagrant's is simpler and easier to understand, but less scalable.

[bauerd]

Yeah I understand the difference between the two but I was wondering why people prefer Vagrant over Docker for development environments.

[dasil003]

If I'm deploying to VMs then I prefer Vagrant, if I'm deploying containers then I prefer Docker. It's all about dev/prod parity, at least at the 30,000' view, once you get into specific use cases there may be reason to mix and match.

[mitchty]

For me, because docker doesn't do jack to help with developing in the kernel.

[dominotw]

I think this is one of the edge cases where vagrant is useful over docker. Most ppl here don't do kernel dev though.

[pizza234]

At my company we need to have virtual machines as close as possible (software wise) to our production environment, including the kernel version.

[stephenr]

Because we want a full VM, to very closely mimic production.