Hi, 

I just started using Packer for the first time

I want to use it to create a custom AMI based on Amazon Linux AMI for 
ElasticBeanstalk.
I want to use the base image and install erlang, elixir and Rserve on it.
For this purpose, I wrote a #cloud-config script to declare all the 
dependencies under "packages:", and to declare all the instructions it 
needs to execute, under "runcmd:", 
so that packer during the build will download a 250mb file from 
erlang.com/download, download a git repo for elixir and download R and all 
its dependencies

I have tested the #cloud-config script by launching an ec2 instance and 
supplying it as user-data. Once I had it fully working, I proceeded to 
supplement this script to packer by specifying a user_data_file

The problem that I am experiencing is that packer stops the instance too 
soon for my 250MB file to even get downloaded. The server only stays on for 
like 20-30 seconds and then it abruptly ends it.

Can someone explain to me why Packer is behaving in this way and what 
potential workaround I may consider? 

Thanks in advance.

-- 
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/ec472824-2188-4285-979e-9fbd2a6d8e4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to