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
Alex Brown 0cea0e5c24
Swap width and height when allocating a pty
10 years ago
.github Delete the PR template before submitting. 10 years ago
Godeps Vendor Azure dependencies 10 years ago
builder Remove explicit boolean comparison 10 years ago
command add -color to build -h command 10 years ago
common Removed ftp/ftps schemas since they don't work. 10 years ago
communicator Swap width and height when allocating a pty 10 years ago
contrib Added sleeps to the azure-setup script so it is more likely to converge before running the next command 10 years ago
examples/azure Fix up azure-arm examples: make sure the variable names line up. 10 years ago
fix Added fixer for ssh_key_path 10 years ago
helper Add support for NTLM the WinRM communicator. 10 years ago
packer file provisioner improvements 10 years ago
plugin/example Add example plugin for third-party plugin use 10 years ago
post-processor Add debug logging for the credentials used for S3 in amazon-import 10 years ago
provisioner Add ignore_exit_codes param for puppet-masterless provisioner 10 years ago
scripts Fix problems in release script 10 years ago
template Display better error messages on json.SyntaxError 10 years ago
test Add sftp file transfer support 11 years ago
vendor Vendor Azure dependencies 10 years ago
website Merge pull request #3419 from tylert/vmw-iso-doc-fix 10 years ago
.gitignore Ignore logs from packer tests 11 years ago
.travis.yml Remove go 1.4 from the build matrix 10 years ago
CHANGELOG.md Updated changelog 10 years ago
CONTRIBUTING.md Update go 1.5 references to 1.6 10 years ago
LICENSE LICENSE: MPL2 13 years ago
Makefile Increase test timeout to 30s to accomodate longer Azure test 10 years ago
README.md Fix README build example to work out of box. 10 years ago
Vagrantfile Update go 1.5 references to 1.6 10 years ago
appveyor.yml Update appveyor spec to go 1.6 10 years ago
azure-merge.sh Added merge script to automatically pull in and fix the upstream repo 10 years ago
checkpoint.go Move ConfigFile() and ConfigDir() from package main to packer 11 years ago
commands.go Implemented internal plugins 10 years ago
config.go Switch osext package from mitchellh -> kardianos #2842 10 years ago
log.go command: move more to this package, remove old packages 11 years ago
main.go Fix -debug command line option misbehaviour: forbid stdin redirection to a pipe when run as plugin server 10 years ago
main_test.go Fatal -> Fatalf since we have a format string 10 years ago
panic.go Rename some files, style 11 years ago
signal.go add interrupt handling for SIGTERM [GH-1858] 11 years ago
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 13 years ago
version.go Change version to non-release version 10 years ago

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
  • 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.