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
Chris Bednarski 18f03ec070
Trim the pull request template
10 years ago
.github Trim the pull request template 10 years ago
Godeps Remove unused dependencies; see godep v54 10 years ago
builder fix assign to driveArgs 10 years ago
command Make the build name error message show the original regexp 10 years ago
common Removed ftp/ftps schemas since they don't work. 10 years ago
communicator file provisioner improvements 10 years ago
contrib/zsh-completion Fix zsh-completion 10 years ago
fix Added fixer for ssh_key_path 10 years ago
helper go fmt 10 years ago
packer file provisioner improvements 10 years ago
plugin go fmt 10 years ago
post-processor file provisioner improvements 10 years ago
provisioner Ansible: os.Environ() should always be passed to the ansible command. 10 years ago
scripts Update dist script to sign signature file 10 years ago
template Display better error messages on json.SyntaxError 10 years ago
test Add sftp file transfer support 11 years ago
vendor Remove unused dependencies; see godep v54 10 years ago
website "environmental variable" -> "environment variable" 10 years ago
.gitignore Ignore logs from packer tests 11 years ago
.travis.yml If go version is 1.4 use godeps to restore dependencies 10 years ago
CHANGELOG.md Updated CHANGELOG 10 years ago
CONTRIBUTING.md Update go 1.5 references to 1.6 10 years ago
LICENSE
Makefile If go version is 1.4 use godeps to restore dependencies 10 years ago
README.md Moved the bulk of go setup to CONTRIBUTING.md so it doesn't need to be maintained in two places 10 years ago
Vagrantfile Update go 1.5 references to 1.6 10 years ago
appveyor.yml Updated appveyor script to (hopefully) work with a vendored build on Windows 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
main.go Generate plugins.go from main.go 10 years ago
main_test.go Fatal -> Fatalf since we have a format string 10 years ago
panic.go
signal.go add interrupt handling for SIGTERM [GH-1858] 11 years ago
stdin.go
version.go Bump version.go to 0.9.1 so dev builds don't tell you to update 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 `access_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.