Closed bacardiandwatermelon closed 6 years ago
Scrap that last fix, it then failed when doing the WEF
Downloaded Vagrant 2.0.2 from: https://www.vagrantup.com/downloads.html Debian 64bit vagrant plugin update
In before next error :-D
@bacardiandwatermelon did Vagrant 2.0.2 fix the issue?
Sorry for the delay.. Just to confirm, Ubuntu 17.10 comes with version 1.9.1 https://launchpad.net/ubuntu/artful/+source/vagrant Ubuntu users will need to get an updated version as specified in your minimum requirements :-) The 2.0.2 deb from vagrantup.com looks to have done the trick, got all the VMs up and running. I haven't had much of a chance to play with the lab yet though, so I assume everything is all good :-)
@bacardiandwatermelon to resolve this I added a check to the build scripts that will ensure the installed version of Vagrant is at least 2.0.0 and give the user a warning if not: https://github.com/clong/DetectionLab/blob/master/build_vagrant_only.sh#L25-L28
Description of the issue:
vagrant up causes the following error: /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- winrm-fs (LoadError)
Had to install winrm and winrm-fs plugins Which gave another error: WinRM::WinRMWebService (NameError)
According to this site, one of the gems broke a reference: https://github.com/NetDocuments/rd-winrm-plugin/issues/29
Fix: vagrant plugin install winrm --plugin-version 1.8.1 vagrant plugin install winrm-fs