Details of my current use-case and errors are out on StackOverflow, but I’m using the amazon-chroot builder to spin up a RHEL8 OS on a secondary disk to further perform custom partitioning scheme. The logs are telling me Packer is failing when looking for a snapshot id that doesn’t exist in my account since I’m using a public AMI provided by Red Hat.
==> amibuild.amazon-chroot.source-ami: Gathering information about this EC2 instance...
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Instance ID: i-0d352db9ab0878fa2
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Using AMI Filters {
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Filters: [
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: {
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Name: "virtualization-type",
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Values: ["hvm"]
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: },
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: {
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Name: "architecture",
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Values: ["arm64"]
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: },
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: {
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Name: "name",
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Values: ["RHEL-8.6.0_HVM-*-arm64-2-Hourly2-GP2"]
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: },
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: {
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Name: "root-device-type",
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Values: ["ebs"]
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: },
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: {
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Name: "state",
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Values: ["available"]
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: }
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: ],
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Owners: ["309956199498"]
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: }
amibuild.amazon-chroot.source-ami: Found Image ID: ami-0238411fb452f8275
==> amibuild.amazon-chroot.source-ami: Checking the root device on source AMI...
==> amibuild.amazon-chroot.source-ami: Creating the root volume...
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Obtaining lock: /var/lock/packer-chroot/lock
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Device: /dev/sdh
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Searching for root device of the image (/dev/sda1)
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Create args: {
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: AvailabilityZone: "us-east-1f",
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Encrypted: false,
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: Size: 10,
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: SnapshotId: "snap-0221afb3433c26165",
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: VolumeType: "gp2"
2023/04/05 18:36:21 packer-builder-amazon-chroot plugin: }
==> amibuild.amazon-chroot.source-ami: Error creating root volume: InvalidSnapshot.NotFound: Snapshot does not exist
My account:
❯ aws ec2 describe-snapshots --snapshot-ids snap-0221afb3433c26165
An error occurred (InvalidSnapshot.NotFound) when calling the DescribeSnapshots operation: The snapshot 'snap-0221afb3433c26165' does not exist.
I don’t have access to this snapshot, since it was created under Red Hat’s account, and I’m curious if Packer expects me to be the owner of both the AMI and the underlying EBS snapshot?