What determines the size of the EBS AMI snapshots Packer creates?

[Bruce Johnson]

Hi,

I recently started building my EBS AMI images using an Ubuntu 18.04 base as opposed to an Ubuntu 16.04 base, and noticed that the snapshots created by Packer are now 20GB in size, where previously they were 8GB. I figured this change was the likely cause, but the size of the 18.04 AMI is still 8GB. Any idea what would have caused the snapshots to increase in size like this? Additionally, how can I force them to be smaller?

Thanks,

Bruce

[Rickard von Essen]

This depends on:

ami_block_device_mappings

launch_block_device_mappings

The size of the snapshot in the source_ami

Could you provide some information on what you checked, what your template looks like, and what you changed between the runs.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/1b22c513-1dd5-47b9-a8a3-8e80d18409aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bruce Johnson]

Thanks for the explanation, Rickard. However, it turns out the issue was that my source AMI filter string for 18.04 is no longer specific enough to pull down the image that I want. Having made the filter more specific, it is returning the standard image at 8 GB, rather than the Kubernetes image which is 20 GB.

Thanks,

Bruce