Go to file
DanHam 475b3978d2
Remove tmp directories created by builder/parallels/common tests
2018-04-30 20:38:03 +01:00
.github
builder Remove tmp directories created by builder/parallels/common tests 2018-04-30 20:38:03 +01:00
command Merge branch 'master' into f-autocomplete 2018-04-26 11:18:37 -07:00
common Remove tmp files created by common/ tests 2018-04-30 18:16:46 +01:00
communicator
contrib
examples
fix
helper
packer
plugin/example
post-processor
provisioner Remove script containing Win-Shell inline commands from local tmp when done 2018-04-26 00:32:52 +01:00
scripts
template
test
vendor Merge branch 'master' into f-autocomplete 2018-04-26 11:18:37 -07:00
version update to 1.2.4-dev 2018-04-25 14:32:44 -07:00
website Resolve FOUT Issue 2018-04-27 17:12:00 -04:00
.gitattributes
.gitignore
.travis.yml Merge branch 'master' into f-autocomplete 2018-04-26 11:18:37 -07:00
CHANGELOG.md update changelog 2018-04-26 14:08:48 -07:00
CODEOWNERS
LICENSE
Makefile
README.md
Vagrantfile
appveyor.yml
checkpoint.go
commands.go
config.go
log.go
main.go Merge branch 'master' into f-autocomplete 2018-04-26 11:18:37 -07:00
main_test.go
panic.go
stdin.go

README.md

Packer

Build Status Windows Build Status GoDoc GoReportCard

Packer is a tool for building identical machine images for multiple platforms from a single source configuration.

Packer is lightweight, runs on every major operating system, and is highly performant, creating machine images for multiple platforms in parallel. Packer comes out of the box with support for many platforms, the full list of which can be found at https://www.packer.io/docs/builders/index.html.

Support for other platforms can be added via plugins.

The images that Packer creates can easily be turned into Vagrant boxes.

Quick Start

Download and install packages and dependencies

go get github.com/hashicorp/packer

Note: There is a great introduction and getting started guide for those with a bit more patience. Otherwise, the quick start below will get you up and running quickly, at the sacrifice of not explaining some key points.

First, download a pre-built Packer binary for your operating system or compile Packer yourself.

After Packer is installed, create your first template, which tells Packer what platforms to build images for and how you want to build them. In our case, we'll create a simple AMI that has Redis pre-installed. Save this file as quick-start.json. Export your AWS credentials as the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.

{
  "variables": {
    "access_key": "{{env `AWS_ACCESS_KEY_ID`}}",
    "secret_key": "{{env `AWS_SECRET_ACCESS_KEY`}}"
  },
  "builders": [{
    "type": "amazon-ebs",
    "access_key": "{{user `access_key`}}",
    "secret_key": "{{user `secret_key`}}",
    "region": "us-east-1",
    "source_ami": "ami-af22d9b9",
    "instance_type": "t2.micro",
    "ssh_username": "ubuntu",
    "ami_name": "packer-example {{timestamp}}"
  }]
}

Next, tell Packer to build the image:

$ packer build quick-start.json
...

Packer will build an AMI according to the "quick-start" template. The AMI will be available in your AWS account. To delete the AMI, you must manually delete it using the AWS console. Packer builds your images, it does not manage their lifecycle. Where they go, how they're run, etc. is up to you.

Documentation

Comprehensive documentation is viewable on the Packer website:

https://www.packer.io/docs

Developing Packer

See CONTRIBUTING.md for best practices and instructions on setting up your development environment to work on Packer.