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 5c2ca450bd
fix tests
7 years ago
.github Miscellaneous doc improvements 7 years ago
builder fix tests 7 years ago
command Merge pull request #6871 from LKaemmerling/master 7 years ago
common fix variable casing convention 7 years ago
communicator dont change ssh communicator as part of this pr 7 years ago
contrib Try to make help more consistent 7 years ago
examples Add ansible connection plugin examples 8 years ago
fix bug fix and add test 8 years ago
helper new option allowing user to clean up the ephemeral ssh key from the authorized_keys file 8 years ago
packer fix more race conditions 7 years ago
plugin/example delete unneeded plugin file 9 years ago
post-processor cleanup to make it actually build after that monstrous rebase 7 years ago
provisioner make provisioner/ansible/provisioner_test.go invisible to windows 7 years ago
scripts use xargs to check for formatting 8 years ago
template make template/parse_test.go invisible to windows 7 years ago
test Miscellaneous doc improvements 7 years ago
vendor fix tests 7 years ago
version now dev for 1.3.2 8 years ago
website Copy and paste export related documentation. 7 years ago
.gitattributes too many files for shell during Make, convert .go and .sh to EOL=lf 8 years ago
.gitignore switch to netlify deployment 8 years ago
.travis.yml travis-ci: allow failures on windows 7 years ago
CHANGELOG.md update changelog 7 years ago
CODEOWNERS add scaleway codeowners 8 years ago
LICENSE
Makefile Makefile: make find work on windows using `-executable` instead of `-perm +111` 7 years ago
README.md Miscellaneous doc improvements 7 years ago
Vagrantfile First cut at vagrant post-processor for docker 8 years ago
appveyor.yml revert appveyor skips as windows builds are pretty unstable 7 years ago
checkpoint.go move packer to hashicorp 9 years ago
commands.go Complete Atlas deprecation. 8 years ago
config.go move packer to hashicorp 9 years ago
log.go Use Sprint() instead of Sprintf() in log dedupe 7 years ago
main.go document wrapConfig a little 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.