Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

local-exec provisioner error when building Attack Range at splunk server #1023

Open
Luciel161 opened this issue Dec 17, 2024 · 0 comments
Open

Comments

@Luciel161
Copy link

Luciel161 commented Dec 17, 2024

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).

Screenshot 2024-12-18 015200

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant