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
Rickard von Essen ed273878db
Merge pull request #5576 from dan9186/support-gce-cos-image
8 years ago
.github Updated ISSUE_TEMPLATE.md 9 years ago
builder Adding GCE container optimized os image project 8 years ago
command Merge pull request #5444 from vijayinvites/packer-vhdx 8 years ago
common Merge pull request #5512 from hashicorp/fix5501 8 years ago
communicator SOCKS5 proxy support 8 years ago
contrib Update _packer 9 years ago
examples azure: sysprep improvements for Windows examples 9 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 only output telemetry logs when enabled. 9 years ago
plugin/example delete unneeded plugin file 9 years ago
post-processor Merge pull request #5567 from bennu/vm-template-with-export-vm 8 years ago
provisioner Merge pull request #5563 from hashicorp/fix_5483 8 years ago
scripts build: Allow multi-platform dev with Vagrantfile 8 years ago
template Unit test to verify that parsing fails on a certain kind of malformed JSON 9 years ago
test Add options to LXC builder for influencing for how containers are built and started 8 years ago
vendor Merge pull request #5439 from pkilar/socks5_proxy 8 years ago
version next version is 1.1.2 8 years ago
website Merge pull request #5563 from hashicorp/fix_5483 8 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 Merge pull request #5206 from sandersaares/hyperv-second-temp-dir 8 years ago
.travis.yml add go 1.9 to travis 9 years ago
CHANGELOG.md update changelog 8 years ago
CODEOWNERS codeowners for post-processors 8 years ago
CONTRIBUTING.md go <= 1.6 are no longer supported 9 years ago
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 fix appveyor 9 years ago
azure-merge.sh
checkpoint.go move packer to hashicorp 9 years ago
commands.go move packer to hashicorp 9 years ago
config.go move packer to hashicorp 9 years ago
log.go Fix debug logging 10 years ago
main.go only output telemetry logs when enabled. 9 years ago
main_test.go move packer to hashicorp 9 years ago
panic.go Add telemetry reporting through checkpoint 9 years ago
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.