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
Andrew Starr-Bochicchio ae1bb856a3
digitalocean-import: Fix panic when 'image_regions' not set (Fixes: #7843).
6 years ago
.circleci pin to go 1.13 & cleanup go deps 7 years ago
.github fix formatting 7 years ago
builder fix structs and regenerate partials 6 years ago
cmd ignore doc fields containing `TODO` 7 years ago
command rename option to error-cleanup-privisoner, which I think is clearer 7 years ago
common rename option to error-cleanup-privisoner, which I think is clearer 7 years ago
communicator fixup: Propagate bind errors up 7 years ago
contrib Fix zsh auto-completion 7 years ago
examples Clarify sysprep log message in Azure example 7 years ago
fix Move fixer test to fix package 7 years ago
helper make friendlier message warning user that their creds may be wrong 7 years ago
packer add test for error-cleanup provisioner, and fix tests by fixing null builder to use an actual none communicator instead of skipping communicator generation altogether 7 years ago
plugin/example delete unneeded plugin file 9 years ago
post-processor digitalocean-import: Fix panic when 'image_regions' not set (Fixes: #7843). 6 years ago
provisioner provisioner/inspec: Fix dropped error 7 years ago
scripts change installation of pigeon if off gopath 7 years ago
template reuse code 6 years ago
test SSH tunneling support 7 years ago
vendor Merge pull request #8131 from hashicorp/fix_8036 6 years ago
version update to version 1.5.0-dev 6 years ago
website fix structs and regenerate partials 6 years ago
.gitattributes refresh line endings 7 years ago
.gitignore scrape builder docs from https://www.packer.io/docs/ 7 years ago
.travis.yml test osx on travis 7 years ago
CHANGELOG.md update changelog 6 years ago
CODEOWNERS Update CODEOWNERS 7 years ago
Dockerfile dockerfile: add minimal image with provisioners support 7 years ago
LICENSE
Makefile Merge remote-tracking branch 'origin/master' into scrape_doc_to_builder_struct_config 7 years ago
README.md Miscellaneous doc improvements 7 years ago
Vagrantfile vagrantfile: add support for docker provider 7 years ago
appveyor.yml remove appveyor and travis cfg files 7 years ago
background_check.go surface notimplemented errs too 7 years ago
background_check_openbsd.go copypasta 7 years ago
checkpoint.go
commands.go implement a packer console analogous to the terraform console 7 years ago
config.go use port as ints 7 years ago
go.mod Cut version 1.4.4 6 years ago
go.sum Cut version 1.4.4 6 years ago
log.go deduplicate loglines that stream both to ui ERROR call and to streaming logs when PACKER_LOG=1 7 years ago
main.go build differently for openbsd because we can't cross compile the process library 7 years ago
main_test.go
panic.go
tty.go allow building packer on solaris by removing progress bar and tty imports 7 years ago
tty_solaris.go allow building packer on solaris by removing progress bar and tty imports 7 years ago

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 many platforms, the full list of which can be found at https://www.packer.io/docs/builders/index.html.

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-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.