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.

Sign up for GitHub

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

Jump to bottom

Packer is leaving a trail of EBS volumes in its wake #2

Closed
1 of 16 tasks
obscurerichard opened this issue Jan 8, 2025 · 1 comment
Closed
1 of 16 tasks

Packer is leaving a trail of EBS volumes in its wake #2

obscurerichard opened this issue Jan 8, 2025 · 1 comment

Comments

@obscurerichard
Copy link

Description

When Packer runs vs. EC2, it does not clean up the volumes left behind after the AMI is created, see #1

Likely we just need to specify delete_on_termination in the spec for the volume. See https://groups.google.com/g/packer-tool/c/GT0s0sqNlHM

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2025

Image version and build link

n/a

Is it regression?

n/a

Expected behavior

The EBS volumes should be deleted

Actual behavior

EBS volumes are left behind after creation, accumulating charges

Repro steps

Bake an image with Packer for AWS
Look at the EBS volumes left behind once Packer is done
@obscurerichard obscurerichard mentioned this issue Jan 9, 2025
Merged
@obscurerichard
Copy link
Author

#1 resolved this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@obscurerichard