Hi,

I'm having trouble building attack_range locally. Despite spending several days troubleshooting, I haven't been able to resolve the issue. I have tried using different machines, including fresh installs of Ubuntu 22.04 and 24.04, but I continue to encounter the same error. Below are the error details:

attack_range is using config at path attack_range_local.conf
2025-01-04 11:56:17,238 - INFO - attack_range - INIT - attack_range v1
2025-01-04 11:56:17,241 - INFO - attack_range - [action] > build

Bringing machine 'attack-range-splunk-server' up with 'virtualbox' provider...
Bringing machine 'attack-range-windows-domain-controller' up with 'virtualbox' provider...
==> attack-range-splunk-server: Importing base box 'generic/ubuntu1804'...

==> attack-range-splunk-server: Matching MAC address for NAT networking...
==> attack-range-splunk-server: Checking if box 'generic/ubuntu1804' version '4.3.12' is up to date...
==> attack-range-splunk-server: Setting the name of the VM: attack-range-splunk-server
==> attack-range-splunk-server: Fixed port collision for 22 => 2222. Now on port 2200.
==> attack-range-splunk-server: Clearing any previously set network interfaces...
==> attack-range-splunk-server: Preparing network interfaces based on configuration...
attack-range-splunk-server: Adapter 1: nat
attack-range-splunk-server: Adapter 2: hostonly
==> attack-range-splunk-server: Forwarding ports...
attack-range-splunk-server: 8000 (guest) => 8000 (host) (adapter 1)
attack-range-splunk-server: 8089 (guest) => 8089 (host) (adapter 1)
attack-range-splunk-server: 22 (guest) => 2200 (host) (adapter 1)
==> attack-range-splunk-server: Running 'pre-boot' VM customizations...
==> attack-range-splunk-server: Booting VM...
==> attack-range-splunk-server: Waiting for machine to boot. This may take a few minutes...

**The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'gurumeditation' state. Please verify everything is configured properly and try again.

If the provider you're using has a GUI that comes with it, it is often helpful to open that and watch the machine, since the GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the VirtualBox GUI is open.

The primary issue for this error is that the provider you're using is not properly configured. This is very rarely a Vagrant issue.
2025-01-04 11:56:29,846 - ERROR - attack_range - vagrant failed to build**