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
Matthew Hooker 09bbd0e1cd
fix tense
10 years ago
.github Clearified how to specify version when reporting issues 10 years ago
builder Merge pull request #3758 from elconas/fix_vmware_builder 10 years ago
command gofmt project. 10 years ago
common builder/amazon: add retry login when creating tags. 10 years ago
communicator log unknown error, make ExitMissingError clearer 10 years ago
contrib Changes How Azure AD Apps are Created 10 years ago
examples/azure azure: Examples of a custom image 10 years ago
fix
helper Fail on unknown values of -on-error 10 years ago
packer Allow upper case input to -on-error=ask 10 years ago
plugin/example
post-processor Added vsphere-esx hosts to supported machine types in vagrant post processor 10 years ago
provisioner Merge pull request #3776 from curiositycasualty/master 10 years ago
scripts Go's -X linker flag now requires only one argument (#3540) 10 years ago
template
test Make SCP the default for provisioner/ansible 10 years ago
vendor bump ssh library, check for ssh.ExitMissingError 10 years ago
version our next release will be 0.11 10 years ago
website fix tense 10 years ago
.gitignore azure: Support for a user define VNET. 10 years ago
.travis.yml
CHANGELOG.md update changelog 10 years ago
CONTRIBUTING.md removes vendor make target 10 years ago
LICENSE
Makefile incorporates feedback from pr 10 years ago
README.md Add Azure to the list of supported platforms 10 years ago
Vagrantfile
appveyor.yml Use the default version of Go. (#3498) 10 years ago
azure-merge.sh
checkpoint.go
commands.go
config.go
log.go Fix debug logging 10 years ago
main.go Added -force truncation behavior for manifest, and added docs 10 years ago
main_test.go
panic.go
signal.go
stdin.go

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.