-
Notifications
You must be signed in to change notification settings - Fork 19
Support libvirt vagrant provider #47
Comments
It works ! I have committed in my libvirt branch the needed change: olberger@69b5d17 |
@olberger Vagrant removed libvirt, are you using a plugin to add libvirt support back in? Would you mind linking documentation on how you were able to get this running? |
I guess I must be using https://github.com/vagrant-libvirt/vagrant-libvirt I think I saw mentions of @cloudtoad struggling with it on twitter yesterday, and maybe he could confirm about the necessary docs additions ? and by the way, you might be interested to have a look at this repo, which demos how to secure containers with KataContainers (re MP3) |
Of course, another option could be to just use minikube which is able to use libvirt directly, when on Linux and if qemu/kvm is preferred... but that reverses the point of using Vagrant genrally :-/ Or we could try Vagrant with no virtualizer to start minikube with qemu... if that's even feasable ?... Too many options ;) |
I'm a bit doubtful on the last one, i.e. vagrant doing pretty much nothing... sorry. |
I added the libvirt provider to the vagrantfile and it works well. You need to update antidote-config.yml to set the provider to libvirt and you need to install the vagrant-libvirt plugin. See: #62 |
It could be interesting to be able to use libvirt (for qemu/kvm) on Linux as an alternative to virtualbox.
Would be interesting to verify any gain on performance...
The text was updated successfully, but these errors were encountered: