I don’t know if I was doing something wrong, but I had a lot of trouble provisioning Vagrant. I got it working and thought I’d share the steps I took in case anyone else is having the same problem.
Issue #1: Virtualization was not enabled in my BIOS
However, my enable virtualization setting was not in the same place as in this video (or the location cited on various web pages). Please see below for a screenshot of where my setting was located:
Issue #2 - Provisioning script could not seem to access the "dataset" folder
The issue seemed to be that the provisioning script could not find the
dataset folder, even though it was present (
Fixing this issue was a 2 step process:
Download and unzip the product files in the
Comment out the line in the provisioning script that was trying to download and unzip these files so that the script would not get generate an error at that point and stop running.
Download and unzip the product files in the "dataset" folder
- Open the file
provision-mongodin a text or code editor (e.g., Visual Studio Code, Notepad++, plain old Notepad, etc.) and find the
Follow the AWS links (ctrl + click in VS Code) for the two product files. Or I am pasting them here for you to follow:
These product files will be downloaded to your computer as zip files. Move them into the
datasetdirectory and unzip them. You can delete the zipped (.tgz) files if you want, as the
download_databasefunction appears to delete them after unzipping. But I kept them.
Comment out the line in the provisioning script and rerun
- In the
provision-mongodfile that is open in your text editor, scroll down to the bottom. Comment out the
download_datasetcommand and save the file:
- Rerun the
vagrant up --provisioncommand on your command line.
I got an error message about my IP address but everything else seemed to work fine. I was able to successfully run the