Go to file
Chris Bednarski b199a6e546 Merge pull request #3376 from kikitux/master
add -color to build -h command
2016-03-24 11:07:27 -07:00
.github Delete the PR template before submitting. 2016-03-07 12:09:01 +01:00
Godeps Vendor Azure dependencies 2016-03-14 20:08:41 -07:00
builder Remove explicit boolean comparison 2016-03-17 14:14:03 -07:00
command add -color to build -h command 2016-03-23 04:40:24 +13:00
common Removed ftp/ftps schemas since they don't work. 2016-02-09 13:02:42 +01:00
communicator Add support for NTLM the WinRM communicator. 2016-03-10 10:53:38 -08:00
contrib Added sleeps to the azure-setup script so it is more likely to converge before running the next command 2016-03-14 20:08:36 -07:00
examples/azure Added example templates for Azure 2016-03-14 20:08:35 -07:00
fix Added fixer for ssh_key_path 2016-02-12 17:24:42 -08:00
helper Add support for NTLM the WinRM communicator. 2016-03-10 10:53:38 -08:00
packer file provisioner improvements 2016-02-12 11:48:28 -08:00
plugin/example Add example plugin for third-party plugin use 2016-03-16 16:42:24 -07:00
post-processor Add debug logging for the credentials used for S3 in amazon-import 2016-03-10 16:52:16 -08:00
provisioner Add ignore_exit_codes param for puppet-masterless provisioner 2016-03-13 23:39:18 -04:00
scripts Fix problems in release script 2016-03-14 21:24:51 -07:00
template Display better error messages on json.SyntaxError 2016-02-10 14:52:26 -05:00
test Add sftp file transfer support 2015-07-26 23:49:18 +00:00
vendor Vendor Azure dependencies 2016-03-14 20:08:41 -07:00
website Fix WinRM default SSL port typo. 2016-03-22 11:32:03 +00:00
.gitignore Ignore logs from packer tests 2015-10-14 16:31:43 -07:00
.travis.yml Remove go 1.4 from the build matrix 2016-03-14 21:00:23 -07:00
CHANGELOG.md Updated changelog 2016-03-15 16:06:19 -07:00
CONTRIBUTING.md Update go 1.5 references to 1.6 2016-02-17 16:29:38 -08:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile Increase test timeout to 30s to accomodate longer Azure test 2016-03-14 20:46:22 -07:00
README.md Fix README build example to work out of box. 2016-03-16 22:16:35 -04:00
Vagrantfile Update go 1.5 references to 1.6 2016-02-17 16:29:38 -08:00
appveyor.yml Update appveyor spec to go 1.6 2016-03-17 14:17:49 -07:00
azure-merge.sh Added merge script to automatically pull in and fix the upstream repo 2016-03-14 20:08:12 -07:00
checkpoint.go Move ConfigFile() and ConfigDir() from package main to packer 2015-10-16 17:32:36 -07:00
commands.go Implemented internal plugins 2015-10-21 16:57:38 -07:00
config.go Switch osext package from mitchellh -> kardianos #2842 2015-11-04 12:36:00 -08:00
log.go command: move more to this package, remove old packages 2014-10-27 20:31:02 -07:00
main.go Fix -debug command line option misbehaviour: forbid stdin redirection to a pipe when run as plugin server 2016-03-13 13:14:44 +03:00
main_test.go Fatal -> Fatalf since we have a format string 2015-10-21 16:57:38 -07:00
panic.go Rename some files, style 2014-10-27 20:42:41 -07:00
signal.go add interrupt handling for SIGTERM [GH-1858] 2015-06-08 21:28:36 -07:00
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 2013-07-25 23:27:13 -07:00
version.go Change version to non-release version 2016-03-16 10:06:33 -07:00

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 `secret_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.