From 87896a7d79ecfe06d2538e719061d6e75e1d7952 Mon Sep 17 00:00:00 2001 From: Micah Anderson Date: Tue, 21 Nov 2017 10:05:14 -0500 Subject: Docs: Update docs to prepare for 0.10.0 release Fixes: #8427, #8812 --- docs/en/tutorials/vagrant/index.html | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'docs/en/tutorials/vagrant') diff --git a/docs/en/tutorials/vagrant/index.html b/docs/en/tutorials/vagrant/index.html index 95bd6b71..181a3ccf 100644 --- a/docs/en/tutorials/vagrant/index.html +++ b/docs/en/tutorials/vagrant/index.html @@ -437,12 +437,12 @@ $ leap local save web1

Clone the platform with

-
git clone --recursive -b develop https://github.com/leapcode/leap_platform.git
+
git clone https://leap.se/git/leap_platform
 

 
 
Start the vagrant box with

 
-
cd leap_platform
+
cd leap_platform/tests/example-provider
 vagrant up
 

 
@@ -531,7 +531,7 @@ started by the bitmask client:

 sudo apt-get install ruby-dev libxslt-dev libxml2-dev libvirt-dev
 
 # install the required plugins
-vagrant plugin install vagrant-libvirt fog fog-libvirt sahara
+vagrant plugin install vagrant-libvirt sahara
 

 
 
Log out and then log back in.

@@ -585,8 +585,6 @@ virsh pool-autostart vagrant
 
  • Call to virConnectOpen failed: internal error: Unable to locate libvirtd daemon in /usr/sbin (to override, set $LIBVIRTD_PATH to the name of the libvirtd binary) - you don’t have the libvirtd daemon running or installed, be sure you installed the ‘libvirt-bin’ package and it is running
    • 
 
  • Call to virConnectOpen failed: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied - you need to be in the libvirt group to access the socket, do ‘sudo adduser  libvirtd’ and then re-login to your session.
    • 
 
  • if each call to vagrant ends up with a segfault, it may be because you still have virtualbox around. if so, remove virtualbox to keep only libvirt + KVM. according to https://github.com/pradels/vagrant-libvirt/issues/75 having two virtualization engines installed simultaneously can lead to such weird issues.
    • 
-
  • see the vagrant-libvirt issue list on github
    • 
-
  • be sure to use vagrant-libvirt >= 0.0.11 and sahara >= 0.0.16 (which are the latest stable gems you would get with vagrant plugin install [vagrant-libvirt|sahara]) for proper libvirt support,
    • 
 
 
 
-- 
cgit v1.2.3