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 6fc3c4eb49
properly document how to set boot_wait to 0s
6 years ago
.circleci add docker config 6 years ago
.github Merge pull request #9006 from hashicorp/provisioner_acc_contributing 6 years ago
builder update generated pages after rebase 6 years ago
cmd fix generation script, bugfixes in source comments, update website paths in primary codebase 6 years ago
command packer.io prefix removal, html extension remove for in-code errors 6 years ago
common properly document how to set boot_wait to 0s 6 years ago
communicator packer.io prefix removal, html extension remove for in-code errors 6 years ago
contrib
examples
fix
hcl2template packer.io prefix removal, html extension remove for in-code errors 6 years ago
helper fix generation script, bugfixes in source comments, update website paths in primary codebase 6 years ago
packer
plugin/example
post-processor Merge pull request #8679 from kwibus/gcp-fallback-image 6 years ago
provisioner Merge pull request #9011 from hashicorp/powershell-acceptance-test 6 years ago
scripts scripts/prepare_changelog: Update unescape parenthesis for improved matching 6 years ago
template packer.io prefix removal, html extension remove for in-code errors 6 years ago
test
vendor Rebasing with origin/master and fixing issues 6 years ago
version update to v1.5.6-dev 6 years ago
website linkcheck correction 6 years ago
.codecov.yml Add after_n_builds to codecov.yml (#8913) 6 years ago
.gitattributes
.gitignore
.golangci.yml
.hashibot.hcl update hashibot config not to comment when locking super old and stale issues 6 years ago
CHANGELOG.md update changelog 6 years ago
CODEOWNERS fix generation script, bugfixes in source comments, update website paths in primary codebase 6 years ago
Dockerfile
LICENSE
Makefile fix generation script, bugfixes in source comments, update website paths in primary codebase 6 years ago
README.md Add Codecov badge and remove report style (#8896) 6 years ago
Vagrantfile
appveyor.yml
background_check.go
background_check_openbsd.go
checkpoint.go
commands.go
config.go
config_test.go
go.mod Rebasing with origin/master and fixing issues 6 years ago
go.sum Rebasing with origin/master and fixing issues 6 years ago
log.go
main.go
main_test.go
panic.go
tty.go
tty_solaris.go

README.md

Packer

Build Status Windows Build Status GoDoc GoReportCard codecov

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.