You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, Recently, I encountered an error with the Attack Range. Whenever the creation of the Windows server is completed and moves on to the Splunk server, it always outputs the error of "local-exec provisioner error" as seen in the image attached. I have tried deploying the Attack Range through the provided Docker Image and container and running the scripts on my local machine and my Azure DevOps Pipeline. The only thing I did differently was modify the instances of Windows Server and Splunk Server to "t3.large" in resources.tf files due to my resource restriction. I do not know if that action could be the cause of that problem. I destroyed every failed deployment before building the attack range again. I hope you guys can take a look through this. Much appreciated.
Details of setups I have tried:
Pulling the Docker Image and building the container on an Ubuntu 24.04 WSL locally.
Run the scripts directly on the WSL without using Docker.
Pulling the Docker Image and building the container on an AzureDevOps pipeline with a Microsoft Hosted Agent (Ubuntu).
Run the scripts directly on an AzureDevOps pipeline with a Microsoft Hosted Agent (Ubuntu).
The text was updated successfully, but these errors were encountered:
Hi, Recently, I encountered an error with the Attack Range. Whenever the creation of the Windows server is completed and moves on to the Splunk server, it always outputs the error of "local-exec provisioner error" as seen in the image attached. I have tried deploying the Attack Range through the provided Docker Image and container and running the scripts on my local machine and my Azure DevOps Pipeline. The only thing I did differently was modify the instances of Windows Server and Splunk Server to "t3.large" in resources.tf files due to my resource restriction. I do not know if that action could be the cause of that problem. I destroyed every failed deployment before building the attack range again. I hope you guys can take a look through this. Much appreciated.
Details of setups I have tried:
The text was updated successfully, but these errors were encountered: