Appreciate your reply Megan and Tarun. The idea for to have boot_wait and boot_command is, During booting process, It asks few yes/no questions. There I need to pass appropriate answer. Once the booting process is done. I will modify my code to show up a final question. Based on yes/no inputs, it will shutdown/halt the machine.
Is that can be done user "*user_data" *or *"user_data_file" *? I am sorry if i am asking very basic informations. I am totally new to this packer . On Wednesday, December 16, 2020 at 11:06:58 PM UTC+5:30 Megan Marsh wrote: > The closest thing Amazon builder has to boot commands is the "user_data" > or "user_data_file" field, which will run scripts for you once the image is > booted. > > On Wed, Dec 16, 2020 at 5:52 AM 'Tarun Mittal' via Packer < > [email protected]> wrote: > >> Boot configuration is not there in the amazon-ebs builders, that's why >> you faced this issue. It is available in other builders like virtualbox-iso >> >> On Wednesday, December 16, 2020 at 4:37:32 PM UTC+5:30 >> [email protected] wrote: >> >>> Hello Team, >>> >>> I am trying to create a AWS centos AMI using packer template, where I >>> need to wait for the boot completion and some boot commands as well. I am >>> using builders boot_wait and boot_command parameters. While validating the >>> template i am getting below error. >>> >>> Error: Failed to prepare build: "amazon-ebs" >>> >>> 2 errors occurred: >>> * unknown configuration key: '"boot_command"' >>> * unknown configuration key: '"boot_wait" >>> >>> packer version : 1.6.5 >>> >>> Detailed has been post in : >>> https://stackoverflow.com/questions/65312043/is-packer-support-boot-wait-and-boot-command-for-aws-ami-generation >>> >>> Let me know if anyone have faced this issue ? >>> >> >> *Note:* This message is the property of HashedIn and its subsidiaries. >> It may be legally privileged and/or confidential and is intended only for >> the use of the addressee(s). No addressee should forward, print, copy, or >> otherwise reproduce this message in any manner that would allow it to be >> viewed by any individual not originally listed as a recipient. If the >> reader of this message is not the intended recipient, you are hereby >> notified that any unauthorized disclosure, dissemination, distribution, >> copying or the taking of any action in reliance on the information herein >> is strictly prohibited. If you have received this communication in error, >> please immediately notify the sender and delete this message. >> >> -- >> 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/hashicorp/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/1ca16f23-078f-41b8-a753-6af94a8ec391n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/packer-tool/1ca16f23-078f-41b8-a753-6af94a8ec391n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/hashicorp/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/f79be5cb-7dd3-451d-9595-4f5016af4581n%40googlegroups.com.
