3 ms·

There are still times I look to Vagrant instead of, and alongside, Docker. The reason being Docker for Mac uses a VM anyway (an xhvye machine) - it does try to

There are still times I look to Vagrant instead of, and alongside, Docker. The reason being Docker for Mac uses a VM anyway (an xhvye machine) - it does try to hide/abstract this away, but inevitably this leaks. The xhyve VM has the usual parameters memory, diskspace, CPUs, and not least a kernel. There are limited options to fiddle with these parameters, though you can log into it and poke around there. I thus find it easier to just have setup Vagrant machines with Docker - then I have better control over those things. If I were on a Linux distro though, I'd probably use Vagrant a lot less.

alinspired 9y ago
Vagrant with KVM/libvirt works great on Linux and doesn't stop you from using docker. VirtualBox is inconvenience on Linux, not Vagrant
- hmsimha 9y ago
  Mostly, though the vagrant-libvirt provider is still a separate plugin, and hasn't reached 1.0 yet, probably due to several rough edges. edit: I should also mention that vagrant-libvirt doesn't even work on Vagrant 2.0.0, due to https://github.com/vagrant-libvirt/vagrant-libvirt/issues/768 https://github.com/vagrant-libvirt/vagrant-libvirt/issues/76...
- fulafel 9y ago
  The community is built on Vagrant-VB configs and images, so you don't really get the main benefit of Vagrant if you want to use it with something else than VirtualBox.
  - 4ad 9y ago
    I disagree by saying that I don't think you really get the main benefit of Vagrant if you want to use it with other people's boxes. Also, since the rise of virtio (thank goodness), you can easily make boxes that work on VB/VMware/KVM, and probably others too, and indeed, many boxes work like that.
trengrj 9y ago
Yeah agreed. I just wasted 2 hours this week compacting my qcow2 docker image for my mac (by filling it with zeros). It was totally unintuitive that deleting images didn't free disk space.
scaryclam 9y ago
I use linux, and while I use docker-compose for running many services together, I rarely bother with it for other work. It can misbehave pretty badly and making changes can mean long build times, so I still keep a surprising amount of stuff on vagrant setups.

alinspired 9y ago

Vagrant with KVM/libvirt works great on Linux and doesn't stop you from using docker. VirtualBox is inconvenience on Linux, not Vagrant

hmsimha 9y ago
Mostly, though the vagrant-libvirt provider is still a separate plugin, and hasn't reached 1.0 yet, probably due to several rough edges. edit: I should also mention that vagrant-libvirt doesn't even work on Vagrant 2.0.0, due to https://github.com/vagrant-libvirt/vagrant-libvirt/issues/768 https://github.com/vagrant-libvirt/vagrant-libvirt/issues/76...
fulafel 9y ago
The community is built on Vagrant-VB configs and images, so you don't really get the main benefit of Vagrant if you want to use it with something else than VirtualBox.
- 4ad 9y ago
  I disagree by saying that I don't think you really get the main benefit of Vagrant if you want to use it with other people's boxes. Also, since the rise of virtio (thank goodness), you can easily make boxes that work on VB/VMware/KVM, and probably others too, and indeed, many boxes work like that.

trengrj 9y ago

Yeah agreed. I just wasted 2 hours this week compacting my qcow2 docker image for my mac (by filling it with zeros). It was totally unintuitive that deleting images didn't free disk space.

scaryclam 9y ago

I use linux, and while I use docker-compose for running many services together, I rarely bother with it for other work. It can misbehave pretty badly and making changes can mean long build times, so I still keep a surprising amount of stuff on vagrant setups.