amazon chroot builder doesn't work with new EC2 instance types

[ghost]

This issue was originally opened by @tjbaker as hashicorp/packer#6710. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.

---

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

With the following instances, EBS volumes are exposed as NVMe block devices: C5, C5d, i3.metal, M5, M5d, R5, R5d, T3, and z1d. The device names are /dev/nvme0n1, /dev/nvme1n1, and so on. The device names that you specify in a block device mapping are renamed using NVMe device names (/dev/nvme[0-26]n1).

The Packer chroot builder does not know about this change and fails.

amazon-chroot: Checking the root device on source AMI...
amazon-chroot: Error finding available device: device prefix could not be detected

https://github.com/hashicorp/packer/blob/78c0b7bd9c1c2464c407fadbed3da4e94e627796/builder/amazon/chroot/device.go#L42-L45

[zipkid]

Hello,

What is the status of this issue... ?

Kind regards.

[rnsc]

Any update on @tjbaker initial's request? Is this not a trivial change?

[benbridts]

This is still a problem with the latest version of the plugin:

Installed plugin github.com/hashicorp/amazon v1.3.2

amazon-chroot: Error finding available device: device prefix could not be detected

[AgentK9]

This is still an issue