Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Rickard von Essen 2fea167294
cloudstack: Updated after review
9 years ago
.github Updated ISSUE_TEMPLATE.md 9 years ago
builder cloudstack: Updated after review 9 years ago
command make sure that flagVars is not a nil map 9 years ago
common post-processor/vagrant-cloud: try upload once 9 years ago
communicator Merge pull request #4748 from greenhouse-org/download-winrm 9 years ago
contrib add sleep and retry to azure setup script 9 years ago
examples azure: fit and finish 9 years ago
fix builder/amazon: Change shutdown_behaviour to shutdown_behavior 9 years ago
helper Add 'winrm_use_ntlm' configuration directive for NTLM authentication support 9 years ago
packer move wait earlier 9 years ago
plugin/example move packer to hashicorp 9 years ago
post-processor post-processor/checksum: properly interpolate output 9 years ago
provisioner fix wording 9 years ago
scripts comments 9 years ago
template Unit test to verify that parsing fails on a certain kind of malformed JSON 9 years ago
test add ansible tests for docker builder 9 years ago
vendor Update dependency osext to support Android 9 years ago
version updating to dev version 1.0.4 9 years ago
website update version to 1.0.3 9 years ago
.gitattributes On windows a lot of git clients will convert LF to CRLF. This would be a problem where file contents are compared exactly 9 years ago
.gitignore Add IntelliJ project files to .gitignore 9 years ago
.travis.yml test on travis with go 1.8.3 9 years ago
CHANGELOG.md update changelog in prep for 1.0.3 9 years ago
CONTRIBUTING.md Fixed readme.md and contributing.md 9 years ago
LICENSE LICENSE: MPL2 13 years ago
Makefile run docs through pandoc 9 years ago
README.md Minor fixes 9 years ago
Vagrantfile Update go 1.5 references to 1.6 10 years ago
appveyor.yml fix appveyor 9 years ago
azure-merge.sh Added merge script to automatically pull in and fix the upstream repo 10 years ago
checkpoint.go move packer to hashicorp 9 years ago
commands.go move packer to hashicorp 9 years ago
config.go move packer to hashicorp 9 years ago
log.go Fix debug logging 10 years ago
main.go don't do any logging in realMain. 9 years ago
main_test.go move packer to hashicorp 9 years ago
panic.go Add telemetry reporting through checkpoint 9 years ago
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 13 years ago

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.