how to expand root volume on EC2 instance

[Shalin Patel]

Hi

 I am trying to create new AMI based off official coreos AMI. I am trying to expand root volume to bigger size. When I run packer, the instance is created, volume is generated and attached. However the aws instance is immediately stopped by AWS. There is no system log available in ec2. 

I provided following coniguration

"launch_block_device_mappings": [

                {

                    "device_name": "/dev/sda1",

                    "volume_size": 60,

                    "volume_type": "gp2",

                    "delete_on_termination": true

                }

            ],

"ami_block_device_mappings": [

                {

                    "delete_on_termination" : true,

                    "device_name": "/dev/sdf",

                    "volume_size": 128,

                    "volume_type": "gp2"

                }

            ]

[Rickard von Essen]

I think you shouldn't use launch_block_device_mappings that will replace the (source) ami snapshot with a 60 GB empty ebs volume. 

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/ff08c0ac-b3dd-4d5c-932b-7cc6fbbd8a92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.