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
Mitchell Hashimoto eb02dad16c
add issues URL in crash detect output
13 years ago
builder builder/virtualbox: guest-additions_url can use Version var [GH-272] 13 years ago
command command/inspect: template-build should be template-builder 13 years ago
common common/json: add Unmarshal with method with syntax errors 13 years ago
communicator/ssh communicator/ssh: fix panic when client is nil on reconnect 13 years ago
packer packer: Parallelize synopsis lookup to speed up help output 13 years ago
plugin command/inspect: Inspect a templates contents 13 years ago
post-processor/vagrant post-processor/vagrant: properly close file handles [GH-100] 13 years ago
provisioner provisioner/salt-masterless: switch replace to that prior replace works 13 years ago
scripts scripts: full SHA1 in build, not short 13 years ago
website website: document inspect machine-readable types 13 years ago
.gitignore .gitignore the /src directory 13 years ago
.travis.yml notifications for travis 13 years ago
CHANGELOG.md Enable panicwrap and put crash logs in crash.log 13 years ago
CONTRIBUTING.md Add instructions for how to get Go set up to contribute. 13 years ago
LICENSE LICENSE: MPL2 13 years ago
Makefile add `make deps` 13 years ago
README.md README: move CreateTime to timestmap 13 years ago
config.go command/inspect: Inspect a templates contents 13 years ago
configfile.go Don't depend on os/user anymore, which requires cgo 13 years ago
configfile_unix.go Don't depend on os/user anymore, which requires cgo 13 years ago
configfile_windows.go Don't depend on os/user anymore, which requires cgo 13 years ago
packer.go Enable panicwrap and put crash logs in crash.log 13 years ago
packer_test.go Fix packer test 13 years ago
panic.go add issues URL in crash detect output 13 years ago
signal.go ctrl-c closes stdin for plugins so that they are unblocked 13 years ago
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 13 years ago

README.md

Packer

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 creating AMIs (EC2), VMware images, and VirtualBox images. Support for more 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. Be sure to replace any credentials with your own.

{
  "builders": [{
    "type": "amazon-ebs",
    "access_key": "YOUR KEY HERE",
    "secret_key": "YOUR SECRET KEY HERE",
    "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

Full, comprehensive documentation is viewable on the Packer website:

http://www.packer.io/docs

Developing Packer

If you wish to work on Packer itself, you'll first need Go installed (version 1.1+ is required). Make sure you have Go properly installed, including setting up your GOPATH.

For some additional dependencies, Go needs Mercurial to be installed. Packer itself doesn't require this but a dependency of a dependency does.

Next, clone this repository into $GOPATH/src/github.com/mitchellh/packer and then just type make. In a few moments, you'll have a working packer executable:

$ make
...
$ bin/packer
...

You can run tests by typing make test.

This will run tests for Packer core along with all the core builders and commands and such that come with Packer.