Go to file
Matthew Hooker 220709b7eb Merge pull request #4002 from mitchellh/b-plugin-discovery
Supress plugin discovery from plugins, which is redundant and noisy in the logs
2016-10-13 20:17:43 -07:00
.github Clearified how to specify version when reporting issues 2016-08-25 08:46:42 +02:00
builder Merge pull request #3996 from boumenot/pr-issue-3968 2016-10-13 13:39:54 -07:00
command gofmt project. 2016-09-29 14:13:06 -07:00
common Fixed formatting 2016-10-11 23:43:50 +02:00
communicator log unknown error, make ExitMissingError clearer 2016-10-06 11:13:39 -07:00
contrib Changes How Azure AD Apps are Created 2016-08-24 11:59:21 +01:00
examples/azure azure: Examples of a custom image 2016-08-08 09:59:49 -07:00
fix Added fixer for ssh_key_path 2016-02-12 17:24:42 -08:00
helper Fail on unknown values of -on-error 2016-09-17 14:42:21 +00:00
packer Allow upper case input to -on-error=ask 2016-09-16 12:15:00 +00:00
plugin/example Add example plugin for third-party plugin use 2016-03-16 16:42:24 -07:00
post-processor Fixed formatting 2016-10-11 23:43:50 +02:00
provisioner Fixed formatting 2016-10-11 23:43:50 +02:00
scripts Go's -X linker flag now requires only one argument (#3540) 2016-05-17 13:24:04 -07:00
template Display better error messages on json.SyntaxError 2016-02-10 14:52:26 -05:00
test Make SCP the default for provisioner/ansible 2016-09-11 23:58:31 -07:00
vendor Update atlas-go to get ATLAS_TLS_NOVERIFY option for packer push command 2016-10-12 15:04:35 -07:00
version our next release will be 0.11 2016-09-21 13:31:55 -07:00
website azure: Allow user to override size of OS disk 2016-10-12 16:24:04 -07:00
.gitignore azure: Support for a user define VNET. 2016-07-28 21:31:59 -07:00
.travis.yml Remove go 1.4 from the build matrix 2016-03-14 21:00:23 -07:00
CHANGELOG.md update changelog 2016-10-12 16:27:35 -07:00
CONTRIBUTING.md removes vendor make target 2016-10-05 15:50:17 -07:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile incorporates feedback from pr 2016-10-05 16:14:02 -07:00
README.md Add Azure to the list of supported platforms 2016-06-15 10:28:32 -07:00
Vagrantfile Update go 1.5 references to 1.6 2016-02-17 16:29:38 -08:00
appveyor.yml Use the default version of Go. (#3498) 2016-05-04 15:53:36 -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 version to its own package. (#3460) 2016-04-21 13:19:43 -07:00
commands.go Move version to its own package. (#3460) 2016-04-21 13:19:43 -07:00
config.go Change to explicit comparison with MagicCookieValue 2016-10-13 18:14:22 -07:00
log.go Fix debug logging 2016-10-07 21:10:20 +02:00
main.go Added -force truncation behavior for manifest, and added docs 2016-06-10 15:57:01 -07: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

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
  • Azure
  • 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.