Thanks so much! As of August 2016 I was not able to figure this out reading
Packer docs, but your post got me going.
On Saturday, September 7, 2013 at 12:00:12 AM UTC-5, Sean Mackrory wrote:
>
> After more reading, I found that the (ami|launch)_block_device_mappings
> options accomplish this. As an example if anyone else has the same
> question, to make sure my AMI had a 64 GiB root device both when
> provisioning it and when launching the AMI after it was packaged, I
> specified the following configuration for the EBS builder:
>
> "ami_block_device_mappings": [ {
> "device_name": "/dev/sda1",
> "volume_size": 64,
> "delete_on_termination": true
> } ],
> "launch_block_device_mappings": [ {
> "device_name": "/dev/sda1",
> "volume_size": 64,
> "delete_on_termination": true
> } ]
>
>
>
> On Friday, September 6, 2013 3:12:01 PM UTC-7, Sean Mackrory wrote:
>>
>> Is it possible in packer to edit the size of the root volume in the EC2
>> builders in Packer? This is an option when launching an instance using the
>> Classic Wizard in the AWS Web Console, but I don't see any options that
>> apply to the root volume in the documentation.
>>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/packer-tool/ca90fa39-e880-4638-8f9f-3696eb864bb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
