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
Justin Campbell fdaa89681a
Update go-atlas.
9 years ago
.github Clearified how to specify version when reporting issues 10 years ago
builder fix go vet issue. 9 years ago
command Update go-atlas. 9 years ago
common run gofmt 9 years ago
communicator run gofmt 9 years ago
contrib fixes typo 9 years ago
examples/azure azure: Examples of a custom image 10 years ago
fix run gofmt 9 years ago
helper builder/amazon: Allow use of local SSH Agent 9 years ago
packer Merge pull request #3940 from bhcleek/fix-fastpath 9 years ago
plugin/example Add example plugin for third-party plugin use 10 years ago
post-processor Fixed inconsistency between vagrant-libvirt driver and packer QEMU accelerator 9 years ago
provisioner provisioner/ansible: Move info messages to log 9 years ago
scripts say when we finish checking gofmt 9 years ago
template run gofmt 9 years ago
test Make SCP the default for provisioner/ansible 10 years ago
vendor Update go-atlas. 9 years ago
version next version is 0.11.1 9 years ago
website Fixed misspelling of semantics 9 years ago
.gitignore Add IntelliJ project files to .gitignore 9 years ago
.travis.yml Remove go 1.4 from the build matrix 10 years ago
CHANGELOG.md Updated CHANGELOG.md 9 years ago
CONTRIBUTING.md fix broken link 9 years ago
LICENSE
Makefile fail test target if we have gofmt problems 9 years ago
README.md Fixes #4081: Fix broken README link for 'compile Packer yourself'. 9 years ago
Vagrantfile
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 Change to explicit comparison with MagicCookieValue 9 years ago
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.