Only OSX is currently supported as per workshop requirements.
Please ensure the following versions of applications are installed on your machine prior to going any further.
- git
- Virtualbox v5.016 or above (https://www.virtualbox.org/)
- Vagrant v1.8.1 (https://www.vagrantup.com/)
After Vagrant is installed, run the following command to install a required vagrant plugin:
$ vagrant plugin install vagrant-bindfs
Follow these steps to run the vagrant machine.
Clone the repository to your home directory
$ cd ~
$ git clone https://github.com/nathanwebsterdotme/su-trainingvm.git
Bring the Vagrant box up:
$ cd su-trainingvm
$ vagrant up
This vagrant machine uses an NFS folder to allow us to edit code in our local environment. You will see the following message asking for admin permissions to configure this on first run.
==> systemsup: Exporting NFS shared folders... ==> systemsup: Preparing to edit /etc/exports. Administrator privileges will be required...
WARNING: Improper use of the sudo command could lead to data loss or the deletion of important system files. Please double-check your typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
Please enter your local user admin password when prompted to continue the process.
Due to an issue with Puppet provisioning on the first run, some python packages will fail to install and the following error message will be displayed after the first 'vagrant up' is run:
The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.
To ensure the packages are installed correctly, re-run 'vagrant provision' immediately.
$ vagrant provision
This will re-run puppet on the machine which will install the missing packages. You can now SSH on to the Vagrant box if required:
$ vagrant ssh
Don't forget to stop the machine when you are finished:
$ vagrant halt
Contact [email protected]