Go to file
James Nugent 396147b1ee builder/triton: Vendor dependencies 2016-12-24 10:25:31 +01:00
.github
builder builder: add Triton builder 2016-12-24 10:25:31 +01:00
command builder: add Triton builder 2016-12-24 10:25:31 +01:00
common move powershell module to common 2016-12-12 18:34:15 -08:00
communicator various fixes 2016-11-29 14:55:44 +03:00
contrib Changed Service Principal Creation sequence to comply with newer CLI reqs 2016-11-08 00:20:45 -08:00
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 Merge pull request #3940 from bhcleek/fix-fastpath 2016-11-05 19:58:33 +01:00
plugin/example Try to match style of other builders 2016-12-12 22:44:48 +00:00
post-processor fix vagrant box structure 2016-12-12 22:44:17 +00:00
provisioner Run go fmt on files 2016-12-12 22:45:19 +00:00
scripts update windows build script for go compatibility 2016-11-09 15:11:05 -08:00
template print time.Time with %v 2016-12-06 16:47:08 -08:00
test add ansible tests for docker builder 2016-12-09 06:31:52 -08:00
vendor builder/triton: Vendor dependencies 2016-12-24 10:25:31 +01:00
version prep for next version 2016-12-15 13:37:05 -08:00
website add a note about running qemu next to a `common` file. 2016-12-20 17:22:47 -08: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 test with go 1.7 and 1.8beta 2016-12-06 16:32:32 -08:00
CHANGELOG.md Updated CHANGELOG.md 2016-12-21 15:47:32 +01: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
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
main.go
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.