Go to file
Andrew Starr-Bochicchio 6d31470757 Look up snapshot ID based by Droplet, not user. 2016-02-09 11:29:06 -05:00
Godeps Add godeps 2016-02-04 17:33:21 -08:00
builder Look up snapshot ID based by Droplet, not user. 2016-02-09 11:29:06 -05:00
command Merge branch 'deps' 2016-02-05 14:22:00 -08:00
common Removed ftp/ftps schemas since they don't work. 2016-02-09 13:02:42 +01:00
communicator go fmt 2016-02-08 17:34:06 -08:00
contrib/zsh-completion zsh completion 2015-04-04 13:51:59 +03:00
fix Remove deprecated parallels_tools_host_path and guest_os_distribution 2016-02-01 12:25:01 +01:00
helper go fmt 2016-02-08 17:34:06 -08:00
packer Use alternate temp directories for docker 2015-10-20 11:34:14 -07:00
plugin go fmt 2016-02-08 17:34:06 -08:00
post-processor Merge pull request #3139 from vtolstov/shell_local 2016-02-04 18:58:38 -08:00
provisioner go fmt 2016-02-08 17:34:06 -08:00
scripts Removed go get from build scripts since we have these in vendor already 2016-02-05 13:42:27 -08:00
template Fix #2742: Include template line numbers on error 2015-10-25 12:28:06 -07:00
test Add sftp file transfer support 2015-07-26 23:49:18 +00:00
vendor Vendor all dependencies 2016-02-04 17:33:36 -08:00
website Merge pull request #3134 from rickard-von-essen/issue-2701 2016-02-09 13:15:39 +01:00
.gitignore Ignore logs from packer tests 2015-10-14 16:31:43 -07:00
.travis.yml Bump go 1.5 to 1.5.3 2016-01-27 12:47:45 -08:00
CHANGELOG.md Added QEMU boot_command wait duration to changelog 2016-02-04 17:19:33 -08:00
CONTRIBUTING.md Moved the bulk of go setup to CONTRIBUTING.md so it doesn't need to be maintained in two places 2016-02-05 14:21:10 -08:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile Remove tee so exit code 1 is passed up to the shell and properly fails the build when tests are failing 2016-02-08 20:02:56 -08:00
README.md Moved the bulk of go setup to CONTRIBUTING.md so it doesn't need to be maintained in two places 2016-02-05 14:21:10 -08:00
Vagrantfile Use the newer go pre-built binary in vagrant as well, just like travis 2016-01-28 07:14:47 -05:00
appveyor.yml Updated appveyor script to (hopefully) work with a vendored build on Windows 2016-02-05 14:08:58 -08:00
checkpoint.go Move ConfigFile() and ConfigDir() from package main to packer 2015-10-16 17:32:36 -07:00
commands.go Implemented internal plugins 2015-10-21 16:57:38 -07:00
config.go Switch osext package from mitchellh -> kardianos #2842 2015-11-04 12:36:00 -08:00
log.go command: move more to this package, remove old packages 2014-10-27 20:31:02 -07:00
main.go Generate plugins.go from main.go 2016-02-05 11:17:05 -08:00
main_test.go Fatal -> Fatalf since we have a format string 2015-10-21 16:57:38 -07:00
panic.go Rename some files, style 2014-10-27 20:42:41 -07:00
signal.go add interrupt handling for SIGTERM [GH-1858] 2015-06-08 21:28:36 -07:00
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 2013-07-25 23:27:13 -07:00
version.go up version for dev 2015-08-26 21:24:47 -07:00

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
  • 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 `access_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.