In issue #1117, the packer binary can sometimes conflict with the packer binary supplied with cracklib. This documentation update covers this and provides workarounds for affected users.
Updated to same ami as in main readme.md which is from community AMIs
and therefore doesn't require accepting the AWS marketplace terms
before using in Packer build.
This updates the example for adding DigitalOcean
as a provider in the beginning tutorial. It looks
like it hadn't been updated in some time, and
was using old settings. I've updated it and
confirmed it works.
- the listed AMI isn't found
- t2.micros can only be in a VPC(? so said an error), and the docs say
we're using a t1.micro anyway
- Updates to the vagrant file to get the website to build
While running through the getting-started examples, I ran into a strange
error:
packer $ packer validate example.json
Failed to parse template: Error in line 16, char 2: invalid character
'"' after object key:value pair
"provisioners": [{
packer $
The error was not immediately obvious, as this is my first time working
with Packer, and like many users this also happens to be my first time
working with JSON.
Solution:
I was missing a comma after the 'builders' configuration. I'm sure this
is a common problem, so let's specifically mention that in the document.