Hello Dud,
Thanks for sending out this message. I got bitten by the same issue when
transitioning from Jessie AWS AMI to Stretch AWS AMI. And this bug
report helped me a lot to understand the issue.
Not sure if there is some sort of changelog on the Official Debian AWS
image builds?
Thanks,
On Mon, Jun 26, 2017 at 09:55:31AM +0200, Xavier Lembo wrote:
> I've tried today to use my jessie working script on the eu-west-1 stretch
> ami (ami-e79f8781)
>
> My custom ami must have a specific size for first partition, so , i use a
> specific block device mapping.
>
> On the Stretch
Package: cloud.debian.org
Severity: important
User: cloud.debian@packages.debian.org
Usertags: image
Usertags: aws
Hi,
i'm using packer to create a custom AMI from the debian ones.
I've tried today to use my jessie working script on the eu-west-1
stretch ami (ami-e79f8781)
My custom ami