I have a source AMI and I want to bake a new AMI with some additional packages. I have a snapshot with scripts to install these packages. I was wondering what combination of builders/provisioners/etc I would use to create a volume from this snapshot and then install packages to a different volume (root volume). I would then need to unmount the additional volume created from the snapshot so it is not baked into the AMI as well.
My guess was to use an ' amazon-ebsvolume ' builder to create a volume from the snapshot, then use ' amazon-ebs ' builder to actually create the AMI. I am slightly confused, however, on how I would order the events so the AMI created would only have the root volume baked in. I was looking at using ' launch_block_device_mappings '. Is this easily done in packer? In terraform, I can see how to create a volume from a snapshot easily and with packer I see how to create an AMI given a source AMI. Is there a way to do both cleanly in packer? -- 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/76673db5-2111-4159-b948-f78aa7d06bce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
