我将尝试按照这些说明使用Packer.io构建基本的AWS镜像。但是它对我不起作用。
以下是我的模板文件：
那个VPC和子网是我手动创建的临时的。但为什么我必须这样做呢？为什么packer不像我看到它创建临时安全组和密钥对一样创建它们然后再删除它们呢？
此外，即使我添加了这两行代码，它仍然无法创建AMI，因为它遇到SSH超时。为什么？我手动SSH到此VPC中的其他实例没有任何问题。临时的packer实例具有"InstanceState=Running"、"StatusChecks=2/2"和允许来自世界各地的SSH的安全组。
请参见下面packer命令的调试输出：
以下是我的模板文件：
{
"variables": {
"aws_access_key": "",
"aws_secret_key": ""
},
"builders": [{
"type": "amazon-ebs",
"access_key": "{{user `aws_access_key`}}",
"secret_key": "{{user `aws_secret_key`}}",
"region": "us-east-1",
"source_ami": "ami-146e2a7c",
"instance_type": "t2.micro",
"ssh_username": "ubuntu",
"ami_name": "packer-example {{timestamp}}",
# The following 2 lines don't appear in the tutorial.
# But I had to add them because it said this source AMI
# must be launched inside a VPC.
"vpc_id": "vpc-98765432",
"subnet_id": "subnet-12345678"
}]
}
您会注意到，我不得不偏离说明，添加底部的两行（用于VPC和子网）。这是因为我一直收到以下错误：
==> amazon-ebs: Error launching source instance: The specified instance type
can only be used in a VPC. A subnet ID or network interface
ID is required to carry out the request.
(VPCResourceNotSpecified)
那个VPC和子网是我手动创建的临时的。但为什么我必须这样做呢？为什么packer不像我看到它创建临时安全组和密钥对一样创建它们然后再删除它们呢？
此外，即使我添加了这两行代码，它仍然无法创建AMI，因为它遇到SSH超时。为什么？我手动SSH到此VPC中的其他实例没有任何问题。临时的packer实例具有"InstanceState=Running"、"StatusChecks=2/2"和允许来自世界各地的SSH的安全组。
请参见下面packer命令的调试输出：
$ packer build -debug -var 'aws_access_key=MY_ACCESS_KEY' -var 'aws_secret_key=MY_SECRET_KEY' packer_config_basic.json
Debug mode enabled. Builds will not be parallelized.
amazon-ebs output will be in this color.
==> amazon-ebs: Inspecting the source AMI...
==> amazon-ebs: Pausing after run of step 'StepSourceAMIInfo'. Press enter to continue.
==> amazon-ebs: Creating temporary keypair: packer 99999999-8888-7777-6666-555555555555
amazon-ebs: Saving key for debug purposes: ec2_amazon-ebs.pem
==> amazon-ebs: Pausing after run of step 'StepKeyPair'. Press enter to continue.
==> amazon-ebs: Creating temporary security group for this instance...
==> amazon-ebs: Authorizing SSH access on the temporary security group...
==> amazon-ebs: Pausing after run of step 'StepSecurityGroup'. Press enter to continue.
==> amazon-ebs: Launching a source AWS instance...
amazon-ebs: Instance ID: i-12345678
==> amazon-ebs: Waiting for instance (i-12345678) to become ready...
amazon-ebs: Private IP: 10.0.2.204
==> amazon-ebs: Pausing after run of step 'StepRunSourceInstance'. Press enter to continue.
==> amazon-ebs: Waiting for SSH to become available...
==> amazon-ebs: Timeout waiting for SSH.
==> amazon-ebs: Pausing before cleanup of step 'StepRunSourceInstance'. Press enter to continue.
==> amazon-ebs: Terminating the source AWS instance...
==> amazon-ebs: Pausing before cleanup of step 'StepSecurityGroup'. Press enter to continue.
==> amazon-ebs: Deleting temporary security group...
==> amazon-ebs: Pausing before cleanup of step 'StepKeyPair'. Press enter to continue.
==> amazon-ebs: Deleting temporary keypair...
==> amazon-ebs: Pausing before cleanup of step 'StepSourceAMIInfo'. Press enter to continue.
Build 'amazon-ebs' errored: Timeout waiting for SSH.
==> Some builds didn't complete successfully and had errors:
--> amazon-ebs: Timeout waiting for SSH.
==> Builds finished but no artifacts were created.