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 37b3305301
Better varibable naming.
7 years ago
.circleci clean up config.yml and decrease number of parallel processes in build 7 years ago
.github Miscellaneous doc improvements 7 years ago
builder Add DigitalOcean post-processor. 7 years ago
command Add DigitalOcean post-processor. 7 years ago
common Fix a problem when calling Hyper-V\Compare-VM PowerShell cmdlet (#6726) 7 years ago
communicator Add more detail for errors where the problem is that TEMPDIR is filled up 7 years ago
contrib Try to make help more consistent 7 years ago
examples add options for system disk properties 7 years ago
fix Revert "Rename attribute api_access_key to organization_id" 7 years ago
helper communicator/ssh: proper error message 7 years ago
packer more explicit message 7 years ago
plugin/example delete unneeded plugin file 9 years ago
post-processor Better varibable naming. 7 years ago
provisioner Fix powershell provisioner tests 7 years ago
scripts scripts: add gcc package for using gco on build 7 years ago
template Formatting 7 years ago
test Miscellaneous doc improvements 7 years ago
vendor Update vendored godo. 7 years ago
version prepare for next version 7 years ago
website Mention environmental variables in docs. 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 set release version to today 7 years ago
CODEOWNERS Update Scaleway code owners 7 years ago
Dockerfile dockerfile: add minimal image with provisioners support 7 years ago
LICENSE LICENSE: MPL2 13 years ago
Makefile clean up config.yml and decrease number of parallel processes in build 7 years ago
README.md Miscellaneous doc improvements 7 years ago
Vagrantfile vagrantfile: add support for docker provider 7 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
go.mod go mod init github.com/hashicorp/packer 7 years ago
go.sum go mod init github.com/hashicorp/packer 7 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.