Go to file
Dan Schaffer 03436a3745 builder/amazon/chroot: fix no attachments on volume error.
This adds retry logic to the amazon/chroot builder.  The builder
intermittently fails when ec2conn shows the volume in the attached
state but calling Volumes[0].Attachments return an empty array. The
fix adds a retry logic for when Volumes[0].Attachments has len 0 sleep
for 2 seconds and retry up to 30 times.

When the Volumes[0].Attachments is empty I find within 5 seconds the
Volumes[0].Attachments contains the correct value.

The issue is reported in:
https://github.com/mitchellh/packer/issues/1854
2015-04-16 13:06:48 -04:00
builder builder/amazon/chroot: fix no attachments on volume error. 2015-04-16 13:06:48 -04:00
command Allow -create to be passed still for BC 2015-02-04 13:36:06 -05:00
common Better error reporting when a config key in template is Unknown 2015-03-05 10:23:21 +01:00
communicator/ssh communicator/ssh: bind variable value to closure 2015-02-25 05:43:18 +01:00
fix command: move all remaining commands 2014-10-27 20:34:49 -07:00
packer packer: fix formatting directives in test 2015-02-25 05:43:18 +01:00
plugin post-processor/atlas: make it 2014-12-09 16:14:04 -08:00
post-processor post-processor/vagrant-cloud: fix incorrect printf verb types 2015-02-25 05:43:18 +01:00
provisioner provisioner/salt-masterless: fix incorrect printf verb types 2015-02-25 05:43:18 +01:00
scripts scripts: ignore errors on gox for now 2014-09-11 11:51:44 -07:00
test fixed packer --version 2014-12-13 19:40:39 +01:00
website Address some mobile issues 2015-03-19 10:43:25 -04:00
.gitignore Add Vagrantfile for cross cmpiling 2014-09-04 11:35:27 -07:00
.travis.yml Test Go 1.4 2015-01-23 10:20:57 -05:00
CHANGELOG.md Update CHANGELOG 2015-02-24 20:03:27 -05:00
CONTRIBUTING.md Add gox installation instructions to Contributing 2014-06-26 13:55:47 +02:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile Makefile: add vet target 2015-02-25 05:43:18 +01:00
README.md Add Travis CI badge to README 2015-01-23 11:58:23 +09:00
Vagrantfile Remove Vagrant constants [GH-1566] 2014-10-14 15:41:04 -07:00
checkpoint.go fixing version numbers: RCs should be labeled x.x.x-rcx 2015-02-08 07:44:05 +01:00
commands.go hook up push to commands 2014-12-09 16:14:03 -08:00
config.go Clarify the plugin discovery search & priority orders. 2015-03-11 01:20:30 -04:00
config_unix.go website: update website to point to proper directory 2014-09-08 13:44:58 -07:00
config_windows.go website: update website to point to proper directory 2014-09-08 13:44:58 -07:00
log.go command: move more to this package, remove old packages 2014-10-27 20:31:02 -07:00
main.go fixed packer --version 2014-12-13 19:40:39 +01:00
main_test.go Rename some files, style 2014-10-27 20:42:41 -07:00
panic.go Rename some files, style 2014-10-27 20:42:41 -07: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
version.go Update CHANGELOG 2014-12-09 18:57:03 -08:00

README.md

Packer

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. 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 or any of its built-in providers, you'll first need Go installed (version 1.2+ is required). Make sure Go is properly installed, including setting up a GOPATH.

Next, install the following software packages, which are needed for some dependencies:

Then, install Gox, which is used as a compilation tool on top of Go:

$ go get -u github.com/mitchellh/gox

Next, clone this repository into $GOPATH/src/github.com/mitchellh/packer. Install the necessary dependencies by running make updatedeps and then just type make. This will compile some more dependencies and then run the tests. If this exits with exit status 0, then everything is working!

$ make updatedeps
...
$ make
...

To compile a development version of Packer and the built-in plugins, run make dev. This will put Packer binaries in the bin folder:

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

If you're developing a specific package, you can run tests for just that package by specifying the TEST variable. For example below, only packer package tests will be run.

$ make test TEST=./packer
...