Go to file
Matthew Hooker 3ee8cbc1f1 update changelog 2016-11-01 17:28:23 -07:00
.github Clearified how to specify version when reporting issues 2016-08-25 08:46:42 +02:00
builder Merge pull request #4050 from jen20/ssh-agent 2016-11-01 17:27:37 -07:00
command run gofmt 2016-11-01 14:08:04 -07:00
common run gofmt 2016-11-01 14:08:04 -07:00
communicator run gofmt 2016-11-01 14:08:04 -07:00
contrib Changes How Azure AD Apps are Created 2016-08-24 11:59:21 +01:00
examples/azure azure: Examples of a custom image 2016-08-08 09:59:49 -07:00
fix run gofmt 2016-11-01 14:08:04 -07:00
helper builder/amazon: Allow use of local SSH Agent 2016-10-23 21:43:47 -05:00
packer run gofmt 2016-11-01 14:08:04 -07:00
plugin/example
post-processor Fixed formatting 2016-10-11 23:43:50 +02:00
provisioner run gofmt 2016-11-01 14:08:04 -07:00
scripts say when we finish checking gofmt 2016-11-01 14:07:05 -07:00
template run gofmt 2016-11-01 14:08:04 -07:00
test Make SCP the default for provisioner/ansible 2016-09-11 23:58:31 -07:00
vendor Merge pull request #3660 from StackPointCloud/packer-builder-profitbricks 2016-10-31 15:45:24 -07:00
version next version is 0.11.1 2016-10-21 15:38:46 -07:00
website Merge pull request #4050 from jen20/ssh-agent 2016-11-01 17:27:37 -07:00
.gitignore Add IntelliJ project files to .gitignore 2016-10-23 08:04:55 -05:00
.travis.yml
CHANGELOG.md update changelog 2016-11-01 17:28:23 -07:00
CONTRIBUTING.md fix broken link 2016-11-01 11:16:47 -07:00
LICENSE
Makefile fail test target if we have gofmt problems 2016-11-01 14:07:00 -07:00
README.md Fixes #4081: Fix broken README link for 'compile Packer yourself'. 2016-10-27 22:31:57 -05:00
Vagrantfile
appveyor.yml Use the default version of Go. (#3498) 2016-05-04 15:53:36 -07:00
azure-merge.sh
checkpoint.go
commands.go
config.go Change to explicit comparison with MagicCookieValue 2016-10-13 18:14:22 -07:00
log.go Fix debug logging 2016-10-07 21:10:20 +02:00
main.go Added -force truncation behavior for manifest, and added docs 2016-06-10 15:57:01 -07:00
main_test.go
panic.go
signal.go
stdin.go

README.md

Packer

Build Status Windows Build Status

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

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.