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
Brett Wandel 60cb046657
vendored sync/semaphore
7 years ago
.circleci also make sure packer builds with go modules 7 years ago
.github Update CONTRIBUTING.md 7 years ago
builder Revert "Revert "Merge pull request #7391 from carlpett/proxmox-builder"" 7 years ago
command added the ability to limit number of builds running in parallel 7 years ago
common Merge pull request #7480 from BobSilent/fix-hyperv-multiple-hostadapter-same-switch 7 years ago
communicator allow a provisioner to timeout 7 years ago
contrib added the ability to limit number of builds running in parallel 7 years ago
examples Merge pull request #7375 from lrxcy/fix_190220 7 years ago
fix Merge pull request #7456 from hashicorp/do_5770 7 years ago
helper allow a provisioner to timeout 7 years ago
packer use our own copy of iochan.LineReader 7 years ago
plugin/example delete unneeded plugin file 9 years ago
post-processor update code after go mod update 7 years ago
provisioner move retry code into the common/retry pkg and make retry context aware 7 years ago
scripts scripts/build.sh: allow to set build settings when building 7 years ago
template allow to set provisioner timeout from buildfile 7 years ago
test Add chroot in bats tests 7 years ago
vendor vendored sync/semaphore 7 years ago
version update version 7 years ago
website added the ability to limit number of builds running in parallel 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 make sure CI builds with GO111MODULE=off 7 years ago
CHANGELOG.md update changelog 7 years ago
CODEOWNERS Merge branch 'master' into hyperone 7 years ago
Dockerfile dockerfile: add minimal image with provisioners support 7 years ago
LICENSE
Makefile check if running `go mod vendor` has an effect on vendor directory and if so fail 7 years ago
README.md Miscellaneous doc improvements 7 years ago
Vagrantfile vagrantfile: add support for docker provider 7 years ago
appveyor.yml make sure CI builds with GO111MODULE=off 7 years ago
checkpoint.go move packer to hashicorp 9 years ago
commands.go Complete Atlas deprecation. 8 years ago
config.go use port as ints 7 years ago
go.mod up modules and vendor dir 7 years ago
go.sum Revert "Revert "Merge pull request #7391 from carlpett/proxmox-builder"" 7 years ago
log.go Use Sprint() instead of Sprintf() in log dedupe 7 years ago
main.go Close tty on exit (#7411) 7 years ago
main_test.go move packer to hashicorp 9 years ago
panic.go Add telemetry reporting through checkpoint 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.