Go to file
Christopher Boumenot 123c45caca azure: Include missing vendor file
I forgot to execute govendor sync.  Adding the missing file.
2017-06-26 11:13:40 -07:00
.github move packer to hashicorp 2017-04-04 13:39:01 -07:00
builder azure: unit test fixes 2017-06-26 11:13:39 -07:00
command fix tests 2017-06-08 19:12:04 -07:00
common post-processor/vagrant-cloud: try upload once 2017-06-12 17:34:32 -07:00
communicator Merge pull request #4748 from greenhouse-org/download-winrm 2017-05-22 13:35:25 -07:00
contrib add sleep and retry to azure setup script 2017-04-03 17:14:27 -07:00
examples azure: fit and finish 2017-06-26 11:13:39 -07:00
fix builder/amazon: Change shutdown_behaviour to shutdown_behavior 2016-12-14 21:59:16 +01:00
helper Add 'winrm_use_ntlm' configuration directive for NTLM authentication support 2017-06-07 12:08:12 +01:00
packer increase telemetry timeout 2017-06-26 10:36:37 -07:00
plugin/example move packer to hashicorp 2017-04-04 13:39:01 -07:00
post-processor Merge pull request #4996 from hashicorp/mwhooker/4613 2017-06-13 17:40:09 -07:00
provisioner Revert "Universally provide POSIX semantics for the `shell` provisioner." 2017-06-21 16:11:47 -07:00
scripts comments 2017-06-05 12:56:46 -07:00
template Unit test to verify that parsing fails on a certain kind of malformed JSON 2017-05-19 16:42:42 -04:00
test add ansible tests for docker builder 2016-12-09 06:31:52 -08:00
vendor azure: Include missing vendor file 2017-06-26 11:13:40 -07:00
version next version is 1.0.3 2017-06-21 17:29:02 -07:00
website azure: fit and finish 2017-06-26 11:13:39 -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 test on travis with go 1.8.3 2017-06-06 14:50:38 -07:00
CHANGELOG.md update changelog 2017-06-22 18:08:04 -07:00
CONTRIBUTING.md Fixed readme.md and contributing.md 2017-04-08 17:11:23 -04:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile run docs through pandoc 2017-06-14 18:13:46 -07:00
README.md Minor fixes 2017-06-22 00:35:55 -03:00
Vagrantfile Update go 1.5 references to 1.6 2016-02-17 16:29:38 -08:00
appveyor.yml fix appveyor 2017-06-06 11:52:21 -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 packer to hashicorp 2017-04-04 13:39:01 -07:00
commands.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
config.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
log.go Fix debug logging 2016-10-07 21:10:20 +02:00
main.go don't do any logging in realMain. 2017-06-21 15:23:31 -07:00
main_test.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
panic.go Add telemetry reporting through checkpoint 2017-06-15 13:21:11 -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/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.