Go to file
Ali Rizvi-Santiago a3f0308e92 Re-implemented the support for the floppy_files keyword in order to remain backwards-compatible with templates using the old syntax.
Moved the support for recursive paths from the floppy_files keyword to the new floppy_contents keyword.
Shifted some of the code around to add better logging of what's actually being copied.
Added a couple of unit-tests for the new floppy_contents implementation.
Ensured that all files that were being added were also being included in state.FilesAdded so that the older unit-tests will work.
2016-09-12 11:56:25 -05:00
.github Clearified how to specify version when reporting issues 2016-08-25 08:46:42 +02:00
Godeps Merge pull request #3651 from mitchellh/f-manifest-post-processor 2016-07-21 15:55:47 -07:00
builder Re-implemented the support for the floppy_files keyword in order to remain backwards-compatible with templates using the old syntax. 2016-09-12 11:56:25 -05:00
command Generated command/plugin.go using scripts/generate-plugins.go. 2016-08-15 14:36:26 -07:00
common Re-implemented the support for the floppy_files keyword in order to remain backwards-compatible with templates using the old syntax. 2016-09-12 11:56:25 -05:00
communicator Test that null communicator conforms to interface 2016-06-30 16:17:22 -05:00
contrib Changes How Azure AD Apps are Created 2016-08-24 11:59:21 +01:00
examples/azure azure: tag all resources 2016-08-02 11:25:03 -07:00
fix Added fixer for ssh_key_path 2016-02-12 17:24:42 -08:00
helper Add winrm functionality to null provisioner (#2525) 2016-05-18 17:22:53 -07: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 Added some error handling and logs for the GCE export startup script. 2016-08-15 16:25:57 -07:00
provisioner removes unneeded white space 2016-09-01 13:39:44 -06: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 Add sftp file transfer support 2015-07-26 23:49:18 +00:00
vendor Merge pull request #3651 from mitchellh/f-manifest-post-processor 2016-07-21 15:55:47 -07:00
version Update version to dev mode 2016-05-13 14:30:00 -07:00
website Merge pull request #3823 from mitchellh/f-singlebinary 2016-09-12 07:47:15 +02: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 Updated CHANGELOG.md 2016-09-08 11:32:16 +02:00
CONTRIBUTING.md Self documenting Makefile (#3290) 2016-08-14 15:28:29 +02:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile Self documenting Makefile (#3290) 2016-08-14 15:28:29 +02: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 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 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.