iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add note about handling vpc not found errors.

This commit is contained in:
Matthew Hooker 2017-01-05 12:58:22 -08:00
parent 3e186b185d
commit 09ca600ad9
No known key found for this signature in database
GPG Key ID: 7B5F933D9CE8C6A1
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/source/intro/getting-started/build-image.html.md
View File

@ -163,9 +163,11 @@ try to launch the one in the example output above, you will get an error. If you
want to try to launch your AMI, get the ID from the Packer output.
-> **Note:** If you see a `VPCResourceNotSpecified` error, Packer might not be
able to
might not have a VPC set up. You can either try changing the `instance_type` to
`m3.medium`,
able to determine the default VPC, which the `t2` instance types require. This
can happen if you created you AWS account before `2013-12-04`. You can either
change the `instance_type` to `m3.medium`, or specify a VPC. Please see
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/default-vpc.html for more
information.
## Managing the Image