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
Tyler Tidman c8a9d16675
Add new vendoring stuff to vagrantfile
10 years ago
Godeps Add godeps 10 years ago
builder Merge pull request #3135 from rickard-von-essen/issue-2526 10 years ago
command Merge branch 'deps' 10 years ago
common Removed ftp/ftps schemas since they don't work. 10 years ago
communicator go fmt 10 years ago
contrib/zsh-completion zsh completion 11 years ago
fix Remove deprecated parallels_tools_host_path and guest_os_distribution 10 years ago
helper go fmt 10 years ago
packer Use alternate temp directories for docker 10 years ago
plugin go fmt 10 years ago
post-processor Merge pull request #3139 from vtolstov/shell_local 10 years ago
provisioner go fmt 10 years ago
scripts Removed go get from build scripts since we have these in vendor already 10 years ago
template Fix #2742: Include template line numbers on error 10 years ago
test Add sftp file transfer support 11 years ago
vendor Vendor all dependencies 10 years ago
website Merge pull request #3134 from rickard-von-essen/issue-2701 10 years ago
.gitignore Ignore logs from packer tests 11 years ago
.travis.yml Bump go 1.5 to 1.5.3 10 years ago
CHANGELOG.md Added QEMU boot_command wait duration to changelog 10 years ago
CONTRIBUTING.md Moved the bulk of go setup to CONTRIBUTING.md so it doesn't need to be maintained in two places 10 years ago
LICENSE LICENSE: MPL2 13 years ago
Makefile Remove tee so exit code 1 is passed up to the shell and properly fails the build when tests are failing 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 Add new vendoring stuff to vagrantfile 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 command: move more to this package, remove old packages 11 years ago
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 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 up version for dev 11 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.