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 074b170ed4
Fixed exec bit
8 years ago
.github Spelling & checks 8 years ago
builder Fixed exec bit 8 years ago
command Merge pull request #6423 from hashicorp/fix5513 8 years ago
common Updated common/download.go to handle when a connection error happens (response is nil), and reformatted the error that's returned when an HTTP error occurs. 8 years ago
communicator make trailing slash still work 8 years ago
contrib forces az cli to output in JSON where required 8 years ago
examples Add ansible connection plugin examples 8 years ago
fix Ensure amazon-private-ip fixes string values 8 years ago
helper Emit both the host and the communicator to the user during StepConnect. 8 years ago
packer Add to vagrant post-processor support for Azure 8 years ago
plugin/example delete unneeded plugin file 9 years ago
post-processor Add to vagrant post-processor support for Azure 8 years ago
provisioner remove duplicate code from chef provisioner 8 years ago
scripts use xargs to check for formatting 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 Merge pull request #6423 from hashicorp/fix5513 8 years ago
version update to version 1.2.6-dev 8 years ago
website Merge pull request #6546 from mzupan/do-add-tags 8 years ago
.gitattributes too many files for shell during Make, convert .go and .sh to EOL=lf 8 years ago
.gitignore ignore Eclipse project files 8 years ago
.travis.yml add back in tests on latest go, but allow it to fail. 8 years ago
CHANGELOG.md Updated CHANGELOG.md 8 years ago
CODEOWNERS add scaleway codeowners 8 years ago
LICENSE
Makefile Check that only certain files are executable 8 years ago
README.md Remove `go get` from Quick Start as this isn't required to use Packer 8 years ago
Vagrantfile First cut at vagrant post-processor for docker 8 years ago
appveyor.yml fix appveyor 9 years ago
checkpoint.go move packer to hashicorp 9 years ago
commands.go Re-factor version command to use version.FormattedVersion() function. 8 years ago
config.go move packer to hashicorp 9 years ago
log.go Fix debug logging 10 years ago
main.go Merge branch 'master' into f-autocomplete 8 years ago
main_test.go move packer to hashicorp 9 years ago
panic.go Add telemetry reporting through checkpoint 9 years ago
stdin.go Gracefully clean up on SIGTERM 9 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.