From ebff530fa4562d7ea26638e4d52d2972125a7880 Mon Sep 17 00:00:00 2001 From: Syed Ahsan Date: Tue, 8 Oct 2019 11:10:50 -0700 Subject: [PATCH] Vagrant Libvirt Instructions update (#189) * Vagrant Libvirt Instructions update This patch adds the users to the default group so we dont have to use sudo to start the vagrant, as using sudo is not the most optimal route for gems to be properly configured. Signed-off: Syed Ahsan --- clr-k8s-examples/vagrant.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/clr-k8s-examples/vagrant.md b/clr-k8s-examples/vagrant.md index 7474b84..c80eddd 100644 --- a/clr-k8s-examples/vagrant.md +++ b/clr-k8s-examples/vagrant.md @@ -19,11 +19,16 @@ echo "vhost_net" | sudo tee -a /etc/modules Download the latest Debian package from https://www.vagrantup.com/downloads.html and install it followed by vagrant-libvirt ```bash sudo dpkg -i vagrant_${VER}_x86_64.deb -sudo vagrant plugin install vagrant-libvirt +vagrant plugin install vagrant-libvirt ``` +Make sure to add the user to the default group +```bash +usermod --append --groups libvirt `whoami` +``` + Run vagrant ```bash -sudo vagrant up --provider=libvirt +vagrant up --provider=libvirt ``` Note, in order to spin up vagrant to use different CPUS and MEMORY for individual VM's: