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
Chris Bednarski facf27ceeb
Make rdp and vnc links clickable by adding the protocol
9 years ago
.github
builder Make rdp and vnc links clickable by adding the protocol 9 years ago
command Improve delay between key events 9 years ago
common Merge pull request #4398 from mitchellh/portinclusive 9 years ago
communicator integrate new winrm transport interface 9 years ago
contrib
examples/azure
fix builder/amazon: Change shutdown_behaviour to shutdown_behavior 9 years ago
helper integrate new winrm transport interface 9 years ago
packer parallels/vmware: don't wait for shutdown command. 9 years ago
plugin/example Try to match style of other builders 9 years ago
post-processor post-processor/shell-local: expand tests to align with shell provisioner 9 years ago
provisioner post-processor/shell-local: expand tests to align with shell provisioner 9 years ago
scripts update changelog and add prepare script 9 years ago
template print time.Time with %v 9 years ago
test add ansible tests for docker builder 9 years ago
vendor update vendor packages for winrm from upstream 9 years ago
version v0.12.3 9 years ago
website docs/provisioners/shell: safety first 9 years ago
.gitattributes On windows a lot of git clients will convert LF to CRLF. This would be a problem where file contents are compared exactly 9 years ago
.gitignore
.travis.yml test with go 1.7 and 1.8beta 9 years ago
CHANGELOG.md update changelog 9 years ago
CONTRIBUTING.md
LICENSE
Makefile
README.md Merge pull request #4037 from dacamp/readme 9 years ago
Vagrantfile
appveyor.yml
azure-merge.sh
checkpoint.go
commands.go
config.go
log.go
main.go
main_test.go
panic.go
signal.go
stdin.go

README.md

Packer

Build Status Windows Build Status GoDoc GoReportCard

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

Download and install packages and dependencies

go get github.com/mitchellh/packer

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.