Go to file
Matthew Hooker 6696bf1da1 Merge pull request #4389 from mitchellh/rawatlas
don't interpolate atlas variables.
2017-01-12 18:11:17 -08:00
.github
builder Merge pull request #4385 from rickard-von-essen/issue-4383 2017-01-11 11:37:37 -08:00
command don't interpolate atlas variables. 2017-01-12 16:08:54 -08:00
common Merge pull request #4317 from Tadas/fix-ps-noprofile 2017-01-12 22:47:49 +00:00
communicator
contrib
examples/azure
fix builder/amazon: Change shutdown_behaviour to shutdown_behavior 2016-12-14 21:59:16 +01:00
helper Run go fmt on files 2016-12-12 22:45:19 +00:00
packer
plugin/example
post-processor
provisioner Merge pull request #4326 from asteris-llc/feature/converge-provisioner 2017-01-04 10:46:18 -08:00
scripts
template
test
vendor * Contains the SSH fix by @watters of #3840. 2016-12-27 17:05:27 +01:00
version prep for next version 2016-12-15 13:37:05 -08:00
website small documentation typos 2017-01-11 20:43:54 +01:00
.gitattributes
.gitignore
.travis.yml
CHANGELOG.md update changelog 2017-01-11 11:38:49 -08:00
CONTRIBUTING.md
LICENSE
Makefile
README.md Merge pull request #4037 from dacamp/readme 2016-12-26 15:01:10 +01:00
Vagrantfile
appveyor.yml
azure-merge.sh
checkpoint.go
commands.go
config.go
log.go
main.go
main_test.go
panic.go
signal.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 the following platforms:

  • Amazon EC2 (AMI). Both EBS-backed and instance-store AMIs
  • Azure
  • DigitalOcean
  • Docker
  • Google Compute Engine
  • OpenStack
  • Parallels
  • QEMU. Both KVM and Xen images.
  • VirtualBox
  • VMware

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/mitchellh/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-de0d9eb7",
    "instance_type": "t1.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:

http://www.packer.io/docs

Developing Packer

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