Let me provide a working example and a workflow to test this:
1) Launch a Amazon linux EC2 instance with a instance role/profile with the
policy from Packer docs.
2) SSH to the instance, install packer and add the *template.json* from
below.
3) Run sudo packer build template.json
Example amazon-chroot:
{
"builders": [{
"type": "amazon-chroot",
"source_ami": "ami-ea26ce85",
"ami_name": "packer-amazon-chroot {{timestamp}}"
}],
"provisioners": [{
"type": "shell",
"inline": [ "echo Hi > /tmp/hi && ls /" ]
}]
}
On Thursday, September 29, 2016 at 6:29:29 PM UTC+2, Jitendra Drona wrote:
>
> Hi,
>
> Thanks for being patient with me.
>
> Yes, I do know that both ebs and chroot does both the same type of builds,
> what I am trying to do here is to write a "KISS" type of program, which can
> build both the images of ebs and ec2 simultaneously.
>
> Here is the link, which I am using as my reference point
>
> https://vimeo.com/71399041
>
> As per the link, it doesn't require any extra gotchas or any addition of
> the ebs based disks for the chroot builder.
>
> Also, as per the docs
> https://www.packer.io/docs/builders/amazon-chroot.html, it requires only
> keys ami name and source ami, where as the mount points related to ebs or
> any other specs relative to the build are optional, therefore, it is
> supposed to work smooth without any issues related to the volume attachment
> or detachment.
>
> It would be great help, as it is quite confusing related to the chroot
> builder, as I have already provisioned the minimum required options for the
> build.
>
> *Note:* I worked with chroot-mounts, gotchas and other optional values
> required for building the chroot_builder, nothing helped as we are knocking
> back either "chroot_builder:Error creating mount directory: permission
> denied" or "chroot_builder: Error finding available device: available
> device could not be found". Issue isn't not about this build only, as our
> stand-alone chroot builds, where we only have chroot builder, are also
> failing with the same errors.
>
>
> Thanks,
> Jitendra Drona.
>
> On Wednesday, September 28, 2016 at 11:05:55 AM UTC-5, Jitendra Drona
> wrote:
>>
>> Hi,
>>
>> We are using here Packer in our CI/CD process to build and deploy the ec2
>> instances. of-late, we are experiencing the following errors.
>>
>> [image: Inline image 2]
>>
>> [image: Inline image 3]
>>
>> Also, I have attached a sample file that we are trying to build on to
>> provision our instances.
>>
>> Please, let me know if any further information is required.
>>
>> Thanks,
>> Jitendra Drona.
>>
>>
--
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/e6044b75-7a1a-44f4-8ea9-7695129deaea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
