Go to file
Matthew Hooker 754c80d217
create default tags as well
2017-08-11 12:31:05 -07:00
.github
builder create default tags as well 2017-08-11 12:31:05 -07:00
command
common core: iso_checksum_url should strip query param 2017-07-27 07:21:39 +02:00
communicator
contrib
examples fix keypair error for debug mode and increate the wait time to avoid the timeout failure, add the more example 2017-07-20 11:13:59 +08:00
fix
helper
packer quick patch to make ansible work again 2017-07-19 10:28:13 -07:00
plugin/example
post-processor post-processor/checksum: properly interpolate output 2017-07-09 21:50:20 +02:00
provisioner
scripts
template
test
vendor updating govendor imports 2017-07-31 11:47:56 -07:00
version updating to dev version 1.0.4 2017-07-17 17:08:47 -07:00
website Merge pull request #5133 from mayn/fix-docs-provisioners-salt-masterless 2017-07-28 13:09:02 -07:00
.gitattributes
.gitignore
.travis.yml
CHANGELOG.md update changelog 2017-07-27 13:10:15 -07:00
CONTRIBUTING.md go <= 1.6 are no longer supported 2017-07-24 13:27:31 -07:00
LICENSE
Makefile support default GOPATH 2017-07-22 08:45:34 -07:00
README.md
Vagrantfile
appveyor.yml
azure-merge.sh
checkpoint.go
commands.go
config.go
log.go
main.go
main_test.go
panic.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
  • 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.