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
Megan Marsh 3ace5bb91b
simplify FileExistsLocally
8 years ago
.github
builder simplify FileExistsLocally 8 years ago
command Re-factor version command to use version.FormattedVersion() function. 8 years ago
common simplify FileExistsLocally 8 years ago
communicator SOCKS5 proxy support 8 years ago
contrib
examples Merge pull request #5641 from zhuzhih2017/master 8 years ago
fix remove login_email from docker 8 years ago
helper Check if both SSH proxy and basiton are configured 8 years ago
packer try to fix transient test failure 8 years ago
plugin/example
post-processor Set session in state bag 8 years ago
provisioner typo 8 years ago
scripts build: Allow multi-platform dev with Vagrantfile 8 years ago
template Add new `packer_version` function. 8 years ago
test Add options to LXC builder for influencing for how containers are built and started 8 years ago
vendor builder/triton: Add support for Triton RBAC 8 years ago
version prepare for next version 8 years ago
website builder/triton: Add support for Triton RBAC 8 years ago
.gitattributes
.gitignore
.travis.yml travis: update 1.7 and 1.8 go versions 8 years ago
CHANGELOG.md Update CHANGELOG.md 8 years ago
CODEOWNERS codeowners for post-processors 8 years ago
CONTRIBUTING.md
LICENSE
Makefile Merge pull request #5082 from nak3/makefile-copy-binary 8 years ago
README.md use correct oracle builder name 8 years ago
Vagrantfile build: Allow multi-platform dev with Vagrantfile 8 years ago
appveyor.yml
azure-merge.sh
checkpoint.go
commands.go Re-factor version command to use version.FormattedVersion() function. 8 years ago
config.go
log.go
main.go log when loading config from environment 8 years ago
main_test.go
panic.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
  • CloudStack
  • DigitalOcean
  • Docker
  • Google Compute Engine
  • Hyper-V
  • 1&1
  • OpenStack
  • Oracle Cloud Infrastructure
  • Parallels
  • ProfitBricks
  • QEMU. Both KVM and Xen images.
  • Triton (Joyent Public Cloud)
  • VMware
  • VirtualBox

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/hashicorp/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-af22d9b9",
    "instance_type": "t2.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:

https://www.packer.io/docs

Developing Packer

See CONTRIBUTING.md for best practices and instructions on setting up your development environment to work on Packer.