Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
Go HTML Shell CSS Ruby Makefile Other
Permalink
Failed to load latest commit information.
.github Updated ISSUE_TEMPLATE.md Jun 28, 2017
builder Merge pull request #5130 from rickard-von-essen/cloudstack-ssh-agent Jul 17, 2017
command make sure that flagVars is not a nil map Jul 6, 2017
common post-processor/vagrant-cloud: try upload once Jun 13, 2017
communicator Merge pull request #4748 from greenhouse-org/download-winrm May 22, 2017
contrib add sleep and retry to azure setup script Apr 4, 2017
examples azure: fit and finish Jun 26, 2017
fix builder/amazon: Change shutdown_behaviour to shutdown_behavior Dec 14, 2016
helper Add 'winrm_use_ntlm' configuration directive for NTLM authentication … Jun 7, 2017
packer quick patch to make ansible work again Jul 19, 2017
plugin/example move packer to hashicorp Apr 4, 2017
post-processor post-processor/checksum: properly interpolate output Jul 9, 2017
provisioner fix wording Jun 26, 2017
scripts comments Jun 5, 2017
template Unit test to verify that parsing fails on a certain kind of malformed… May 19, 2017
test add ansible tests for docker builder Dec 9, 2016
vendor Update dependency osext to support Android Jul 8, 2017
version updating to dev version 1.0.4 Jul 18, 2017
website digitalocean: docs: Added missing newline Jul 23, 2017
.gitattributes On windows a lot of git clients will convert LF to CRLF. This would b… Dec 12, 2016
.gitignore Add IntelliJ project files to .gitignore Oct 23, 2016
.travis.yml test on travis with go 1.8.3 Jun 6, 2017
CHANGELOG.md update changelog in prep for 1.0.3 Jul 17, 2017
CONTRIBUTING.md go <= 1.6 are no longer supported Jul 24, 2017
LICENSE LICENSE: MPL2 Jun 24, 2013
Makefile support default GOPATH Jul 22, 2017
README.md Minor fixes Jun 22, 2017
Vagrantfile Update go 1.5 references to 1.6 Feb 18, 2016
appveyor.yml fix appveyor Jun 6, 2017
azure-merge.sh Added merge script to automatically pull in and fix the upstream repo Mar 15, 2016
checkpoint.go move packer to hashicorp Apr 4, 2017
commands.go move packer to hashicorp Apr 4, 2017
config.go move packer to hashicorp Apr 4, 2017
log.go Fix debug logging Oct 7, 2016
main.go don't do any logging in realMain. Jun 21, 2017
main_test.go move packer to hashicorp Apr 4, 2017
panic.go Add telemetry reporting through checkpoint Jun 15, 2017
stdin.go ctrl-c closes stdin for plugins so that they are unblocked Jul 26, 2013

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 the following platforms:

  • Amazon EC2 (AMI). Both EBS-backed and instance-store AMIs
  • Azure
  • CloudStack
  • DigitalOcean
  • Docker
  • Google Compute Engine
  • Hyper-V
  • 1&1
  • OpenStack
  • Parallels
  • ProfitBricks
  • QEMU. Both KVM and Xen images.
  • Triton (Joyent Public Cloud)
  • VMware
  • VirtualBox

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.