Go to file
Mitchell Hashimoto 476d870be5 plugin/provisioner-chef-solo: compile 2013-08-27 14:31:42 -07:00
builder Add base support for openstack [GH-155] 2013-08-26 21:57:23 -07:00
command command/build: "end" sentinel in artifact machine-readable output 2013-08-27 13:40:19 -07:00
common communicator/ssh: respect interrupts by not looping on retyr [GH-327] 2013-08-22 11:53:31 -07:00
communicator/ssh communicator/ssh: Trailing slash won't create destination dir 2013-08-25 20:47:10 -07:00
packer communicator/ssh: Trailing slash won't create destination dir 2013-08-25 20:47:10 -07:00
plugin plugin/provisioner-chef-solo: compile 2013-08-27 14:31:42 -07:00
post-processor/vagrant post-processor/vagrant: don't error if unused 2013-08-23 15:31:21 -07:00
provisioner provisioner/chef-solo: remove unused constants and variables 2013-08-27 13:32:59 -07:00
scripts scripts: build go get ./... early to speed up builds 2013-08-21 11:20:55 -07:00
website website: document chef solo provisioner 2013-08-27 14:29:52 -07:00
.gitignore .gitignore the /src directory 2013-06-29 22:16:31 -04:00
.travis.yml Make travis run data race tests 2013-08-21 11:06:01 -07:00
CHANGELOG.md command/build: "end" sentinel in artifact machine-readable output 2013-08-27 13:40:19 -07:00
CONTRIBUTING.md Add instructions for how to get Go set up to contribute. 2013-07-12 14:40:03 -04:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile add `make deps` 2013-08-13 21:42:08 -04:00
README.md README: move CreateTime to timestmap 2013-08-08 17:25:26 -07:00
config.go Add base support for openstack [GH-155] 2013-08-26 21:57:23 -07:00
configfile.go Don't depend on os/user anymore, which requires cgo 2013-06-17 22:10:11 -07:00
configfile_unix.go Don't depend on os/user anymore, which requires cgo 2013-06-17 22:10:11 -07:00
configfile_windows.go Don't depend on os/user anymore, which requires cgo 2013-06-17 22:10:11 -07:00
packer.go Enable panicwrap and put crash logs in crash.log 2013-08-13 23:55:05 -04:00
packer_test.go Fix packer test 2013-08-12 09:19:24 -07:00
panic.go add issues URL in crash detect output 2013-08-13 23:59:59 -04:00
signal.go packer/plugin: confirm cleanup at first signal received 2013-08-24 12:55:25 +02:00
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 2013-07-25 23:27:13 -07:00

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.