>
> yeah I'm not sure exactly, but it sounds like what you are doing should
> work. Does packer
> power off the instance before creating a new AMI out of the disk image? If
> you try to trace
> the steps that packer does on your own (manually) do you get the same
> result?
Well, AWS does power do
On 04/20/2018 11:41 AM, Chad Tindel wrote:
> Dusty-
>
> Unfortunately I had signed up for the digest so there's no way to reply, I
> fixed that problem moving forward.
>
>> I not as familiar with packer. Does it run a kickstart install?
>
> No, it starts up an ec2 instance with a base AMI (a
Dusty-
Unfortunately I had signed up for the digest so there's no way to reply, I
fixed that problem moving forward.
> I not as familiar with packer. Does it run a kickstart install?
No, it starts up an ec2 instance with a base AMI (ami-1690b173 in us-east-2
in this case) and runs whatever comma
On 04/19/2018 05:03 PM, Chad Tindel wrote:
Hi Chad
> 1. I do a packer build and inside that packer build I add a new systemd
> service at /etc/systemd/system/update_route53_mapping.service and I systemctl
> enable update_route53_mapping as well.
>
> I can see that that is done correctly in
1. I do a packer build and inside that packer build I add a new systemd
service at /etc/systemd/system/update_route53_mapping.service and I
systemctl enable update_route53_mapping as well.
I can see that that is done correctly in the packer output.
However when the system boots, it's like none o