Go to file
Taliesin Sisson ca16f33fa3 Use the same configuration style as existing builders
Move builder into correctly named folder
2016-12-12 22:44:02 +00:00
.github Clearified how to specify version when reporting issues 2016-08-25 08:46:42 +02:00
builder Use the same configuration style as existing builders 2016-12-12 22:44:02 +00:00
command Merge pull request #4163 from StackPointCloud/packer-builder-oneandone 2016-12-08 14:07:35 -08:00
common unbreak glob pattern in floppy_files 2016-11-21 16:29:14 +03: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 azure: Examples of a custom image 2016-08-08 09:59:49 -07:00
fix Fix nested pp case 2016-11-21 15:56:20 -08:00
helper Removed default value for ssh_username 2016-11-17 22:30:34 +01:00
packer Merge pull request #3940 from bhcleek/fix-fastpath 2016-11-05 19:58:33 +01:00
plugin Use the same configuration style as existing builders 2016-12-12 22:44:02 +00:00
post-processor Merge pull request #4210 from yoctocloud/fixes 2016-12-12 12:33:19 -08:00
powershell Port of https://github.com/pbolduc/packer-hyperv/ 2016-12-12 22:44:01 +00:00
provisioner Merge pull request #4210 from yoctocloud/fixes 2016-12-12 12:33:19 -08: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 Merge pull request #4209 from bhcleek/ansible-winrm 2016-12-08 22:37:41 -08:00
version 0.12.1 will be next version 2016-11-15 14:16:06 -08:00
website Merge pull request #4209 from bhcleek/ansible-winrm 2016-12-08 22:37:41 -08: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 update changelog 2016-12-12 12:36:31 -08:00
CONTRIBUTING.md fix broken link 2016-11-01 11:16:47 -07: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 Fixes #4081: Fix broken README link for 'compile Packer yourself'. 2016-10-27 22:31:57 -05: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 Move version to its own package. (#3460) 2016-04-21 13:19:43 -07:00
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 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

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.