So executing the following, as per Splunk’s instructions:
Chmod +x deploy_attack_range.sh
./deploy_attack_range.sh
[This script is successful, no errors found so dependencies are happy]
Then trying to build it:
Python attack_range_local.py –a build
[This errors out with the below]
Traceback (most recent call last):
File “attack_range_local.py”, line 4, in
From modules import logger
ImportError: No module named modules
So I tried Python3 and this time stops on an import in line 7:
Python3 attack_range_local.py –a build
[Error below]
Traceback (Most recent call last):
File “attack_range_local.py”, line 7, in
From modules.VagrantController import VagrantController
File “/home/DEVICE/attackrange/attack_range_local/modules/VagrantController.py”, Line 2, in
From jinja2 import Environment, FileSystemLoader
ModuleNotFoundError: No Module named ‘jinja2’
So no matter using Python 2 or 3, it’s not happy with the Py scripts provided by Splunk. We can’t remove the offending module imports because this would have a knock on effect on the code in the body of the script, as it’s written using those modules.
All support welcome.