How to tell packer not to delete the instance used to build the AMI

[Subhashini Radhakrishnan]

Once the packer is finished building an AMI, it terminates the instances used to build the AMI from.

Is there an option to specify not to terminate the instance once AMI is generated successfull?

[Muthu R D]

On your "builders" portion in your JSON, add the below item to keep them registered in there.

"keep_registered": true

Thanks!

Muthu

[Rickard von Essen]

That option doesn't exist for any Amazon builder. And there is no similar option. Why do you want to keep it running? 

--
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/7d0895a6-cf3c-4dde-93b2-e447128a20bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Subhashini Radhakrishnan]

Thank you for the reply... 

we first build a BASE AMI... and then our scripts use the IP Address of the base AMI to build other dependent AMIs to download the package via network share... 

our scripts are built that way to use the IP address of the BASE AMI's instance...

I guess I will have to launch an instance from the BASE AMI and then use it ..

[Subha]

Hi Muthu,

Thanks for your reply. i added keep_registered in the builder section but it failed.. :( 

amazon-ebs output will be in this color.

1 error(s) occurred:

* unknown configuration key: "keep_registered"

--

[lucas.adam.jackson]

Some builders dont have a keep_registered option ... I haven't used this builder but assume that is the case here

Sent from my Samsung Galaxy smartphone.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAEDMBCyN%2Bkij9a0JHXX6NkmjYxhCCKLCEOn5yqV6As9z_vXt%2BA%40mail.gmail.com.

[Alvaro Miranda Aguilera]

Hello

Depending on what you wan, you will think to build a pipeline.

If you want to package ami, then on packer you can do

Packer:

Base AMI -> Intermediate AMI -> Install product A / run scripts -> AMI for product A

Base AMI -> Intermediate AMI -> Install product B / run scripts -> AMI for product B

Base AMI -> Intermediate AMI -> Install product C / run scripts -> AMI for product C

And you will end with r 4 AMI, base + 4 product.

If what you want is take a base AMI and start a box that will be a server.

Then packer may not bet the tool you are after.

Have a look at terraform to create a EC2 server and you could use a provision script to configure the server.

Alvaro

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/2307cc44-1128-4e7e-ac44-86aa18d157f1%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro