attack_range icon indicating copy to clipboard operation
attack_range copied to clipboard

Vagrant Binary missing in the Docker Image

Open joshsecu opened this issue 1 year ago • 0 comments

I followed the docker installation steps and wanted to run the attack range with the build command.

(attack-range-py3.10) root@0870b3970a7c:/attack_range# python attack_range.py build

                          __
                        .d$$b
                      .' TO$;\
                     /  : TP._;
                    / _.;  :Tb|
                   /   /   ;j$j
               _.-"       d$$$$
             .' ..       d$$$$;
            /  /P'      d$$$$P. |\
           /   "      .d$$$P' |\^"l
         .'           `T$P^"""""  :
     ._.'      _.'                ;
  `-.-".-'-' ._.       _.-"    .-"
`.-" _____  ._              .-"

-(.g$$$$$$$b. .' ""^^T$$$P^) .(: / -" /.' /:/; ..'-'-' ")/ /;/; -.-"..--"" " / / ; .-" ..--"" -' : ..--""--.-" (\ .-(
..--"" -\(\/; _. : ;`- :
; bug

By: Splunk Threat Research Team [STRT] - [email protected]

The Vagrant executable cannot be found. Please check if it is in the system path.

Is it intented to follow the installation steps for vagrant etc. afterwards? I wouldn't assume so, given that all binarys should be installed already.

joshsecu avatar Jun 05 '24 10:06 joshsecu