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
Paul Meyer 1fa8255bdb
Update to go-autorest v7.0.6.
10 years ago
.github Accept only bug reports and feature requests 10 years ago
Godeps Update to go-autorest v7.0.6. 10 years ago
builder azure/builder: fix token validity test 10 years ago
command initial import of checksum post-processor (#3492) 10 years ago
common Removed ftp/ftps schemas since they don't work. 10 years ago
communicator Swap width and height when allocating a pty 10 years ago
contrib Added sleeps to the azure-setup script so it is more likely to converge before running the next command 10 years ago
examples/azure Update samples. 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 Resolves vsphere post-processor problems (#3321) 10 years ago
provisioner append ANSIBLE_HOST_KEY_CHECKING correctly (#3568) 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 Add sftp file transfer support 11 years ago
vendor Update to go-autorest v7.0.6. 10 years ago
version Update version to dev mode 10 years ago
website website: darken works_with azure logo 10 years ago
.gitignore Build script for Windows. (#3481) 10 years ago
.travis.yml Remove go 1.4 from the build matrix 10 years ago
CHANGELOG.md Add bug fix for Azure token validity test 10 years ago
CONTRIBUTING.md Add note about only update what we need to update 10 years ago
LICENSE
Makefile Udpdated test/race timeouts to 2m because AWS seems to be taking a while 10 years ago
README.md Fix README build example to work out of box. 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 Move version to its own package. (#3460) 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
  • 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.