Kali linux not provisioned due to insufficient disk size
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 417
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
First of all great project thank you for the work!
I have tried to provision Kali Linux and I have got this error:
╷
│ Error: creating EC2 Instance: operation error EC2: RunInstances, https response error StatusCode: 400, RequestID: 485bc0d4-1207-4f6b-bc19-7df85166ac6b, api error InvalidBlockDeviceMapping: Volume of size 20GB is smaller than snapshot 'snap-0626a34da08068d7a', expect size>= 25GB
│
│ with module.kali-server.aws_instance.kali_machine[0],
│ on modules/kali-server/resources.tf line 18, in resource "aws_instance" "kali_machine":
│ 18: resource "aws_instance" "kali_machine" {
│
Base snapshot is larger than EBS size in TF this probably needs to be increased to work.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in modules/kali-server/resources.tf at the aws_instance.kali_machine resource on line 18, and compare its EBS volume size with the referenced Kali snapshot requirement. Run the Kali provisioning flow to confirm the volume is at least 25 GB and that the EC2 instance is created successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, terraform
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100