Go to file
Matthew Hooker 4fcbf75da9
s/non existent/nonexistent/
2017-03-29 12:38:33 -07:00
.github Clearified how to specify version when reporting issues 2016-08-25 08:46:42 +02:00
builder s/non existent/nonexistent/ 2017-03-29 12:38:33 -07:00
command spell fixes 2017-03-28 20:36:19 -07:00
common remove unnecessary type conversions 2017-03-28 20:36:21 -07:00
communicator check for a couple errors 2017-03-28 20:36:21 -07:00
contrib Changed Service Principal Creation sequence to comply with newer CLI reqs 2016-11-08 00:20:45 -08:00
examples/azure azure: Use a more long term image sku 2017-02-24 10:56:18 -08:00
fix builder/amazon: Change shutdown_behaviour to shutdown_behavior 2016-12-14 21:59:16 +01:00
helper Revert "Use SSH agent when enabled for bastion step" 2017-02-27 11:30:08 -08:00
packer simplify some code 2017-03-28 20:36:20 -07:00
plugin/example Try to match style of other builders 2016-12-12 22:44:48 +00:00
post-processor automagic simplification 2017-03-28 20:36:20 -07:00
provisioner simplify 2017-03-28 20:45:25 -07:00
scripts update changelog and add prepare script 2017-01-20 12:10:13 -08:00
template remove a bunch of dead code. 2017-03-28 20:36:20 -07:00
test add ansible tests for docker builder 2016-12-09 06:31:52 -08:00
vendor update cli library 2017-03-27 23:13:26 -07:00
version next version is 1.1.0 2017-03-16 15:24:52 -07:00
website Removed merge conflict from Docker example web page 2017-03-28 18:12:47 -07:00
.gitattributes On windows a lot of git clients will convert LF to CRLF. This would be a problem where file contents are compared exactly 2016-12-12 22:44:50 +00:00
.gitignore Add IntelliJ project files to .gitignore 2016-10-23 08:04:55 -05:00
.travis.yml travis build 1.8 2017-02-21 11:59:14 -08:00
CHANGELOG.md update changelog 2017-03-24 15:14:18 -07:00
CONTRIBUTING.md some tips on working on forks. 2017-02-09 19:25:09 -08:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile fail test target if we have gofmt problems 2016-11-01 14:07:00 -07:00
README.md update readme with supported providers 2017-03-22 12:08:47 -07:00
Vagrantfile Update go 1.5 references to 1.6 2016-02-17 16:29:38 -08:00
appveyor.yml Use the default version of Go. (#3498) 2016-05-04 15:53:36 -07:00
azure-merge.sh Added merge script to automatically pull in and fix the upstream repo 2016-03-14 20:08:12 -07:00
checkpoint.go Move version to its own package. (#3460) 2016-04-21 13:19:43 -07:00
commands.go remove a bunch of dead code. 2017-03-28 20:36:20 -07:00
config.go simplify some code 2017-03-28 20:36:20 -07:00
log.go Fix debug logging 2016-10-07 21:10:20 +02:00
main.go remove a bunch of dead code. 2017-03-28 20:36:20 -07: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
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 2013-07-25 23:27:13 -07:00

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/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-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:

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.