Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Billie H. Cleek f760ab2fd8
Make SCP the default for provisioner/ansible
10 years ago
.github Clearified how to specify version when reporting issues 10 years ago
Godeps Merge pull request #3651 from mitchellh/f-manifest-post-processor 10 years ago
builder Merge pull request #3756 from ricardclau/floppy_check 10 years ago
command Generated command/plugin.go using scripts/generate-plugins.go. 10 years ago
common tests actually test the floppies 10 years ago
communicator Test that null communicator conforms to interface 10 years ago
contrib Changes How Azure AD Apps are Created 10 years ago
examples/azure azure: tag all resources 10 years ago
fix Added fixer for ssh_key_path 10 years ago
helper Add winrm functionality to null provisioner (#2525) 10 years ago
packer file provisioner improvements 10 years ago
plugin/example Add example plugin for third-party plugin use 10 years ago
post-processor Added some error handling and logs for the GCE export startup script. 10 years ago
provisioner Make SCP the default for provisioner/ansible 10 years ago
scripts Go's -X linker flag now requires only one argument (#3540) 10 years ago
template Display better error messages on json.SyntaxError 10 years ago
test Make SCP the default for provisioner/ansible 10 years ago
vendor Merge pull request #3651 from mitchellh/f-manifest-post-processor 10 years ago
version Update version to dev mode 10 years ago
website Make SCP the default for provisioner/ansible 10 years ago
.gitignore azure: Support for a user define VNET. 10 years ago
.travis.yml Remove go 1.4 from the build matrix 10 years ago
CHANGELOG.md Updated CHANGELOG.md 10 years ago
CONTRIBUTING.md Self documenting Makefile (#3290) 10 years ago
LICENSE LICENSE: MPL2 13 years ago
Makefile Self documenting Makefile (#3290) 10 years ago
README.md Add Azure to the list of supported platforms 10 years ago
Vagrantfile Update go 1.5 references to 1.6 10 years ago
appveyor.yml Use the default version of Go. (#3498) 10 years ago
azure-merge.sh Added merge script to automatically pull in and fix the upstream repo 10 years ago
checkpoint.go Move version to its own package. (#3460) 10 years ago
commands.go Move version to its own package. (#3460) 10 years ago
config.go Switch osext package from mitchellh -> kardianos #2842 10 years ago
log.go command: move more to this package, remove old packages 11 years ago
main.go Added -force truncation behavior for manifest, and added docs 10 years ago
main_test.go Fatal -> Fatalf since we have a format string 10 years ago
panic.go Rename some files, style 11 years ago
signal.go add interrupt handling for SIGTERM [GH-1858] 11 years ago
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 13 years ago

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.