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
Marin Salinas 04534d87ac
chore: change templateCleanOMIName to templateCleanResourceName function
7 years ago
.circleci test that go generated code if what is should be 7 years ago
.github improve contributing.md for windows user 7 years ago
builder chore: change templateCleanOMIName to templateCleanResourceName function 7 years ago
command feature: add bsuvolume builder and acceptance test 7 years ago
common chore: add removed comment in boot_command 7 years ago
communicator add a check and test so that the winrm communicator upload doesn't fail becuase of a nil file pointer 7 years ago
contrib prevent a breaking change so that we can merge the `-parallel-builds` option first. 7 years ago
examples fix typo 7 years ago
fix add a fixer and update docs for spot_price_auto_product 7 years ago
helper Merge pull request #7831 from hashicorp/fix_ssh_interface 7 years ago
packer text/template turns out to swallow custom error types. 7 years ago
plugin/example delete unneeded plugin file 9 years ago
post-processor Merge pull request #7835 from hashicorp/google_oauth 7 years ago
provisioner [Salt] Replace scp with scp + mv to handle non-root case 7 years ago
scripts change installation of pigeon if off gopath 7 years ago
template text/template turns out to swallow custom error types. 7 years ago
test Add Linode Images builder 7 years ago
vendor add missing vendor dependencies 7 years ago
version update to 1.4.3-dev 7 years ago
website website: add outscale bsuvolume website documentation 7 years ago
.gitattributes refresh line endings 7 years ago
.gitignore switch to netlify deployment 8 years ago
.travis.yml add wait so osx builds dont time out 7 years ago
CHANGELOG.md update changelog 7 years ago
CODEOWNERS fixup! fixup! Add Exoscale Import post-processor 7 years ago
Dockerfile dockerfile: add minimal image with provisioners support 7 years ago
LICENSE LICENSE: MPL2 13 years ago
Makefile change installation of pigeon if off gopath 7 years ago
README.md Miscellaneous doc improvements 7 years ago
Vagrantfile vagrantfile: add support for docker provider 7 years ago
appveyor.yml appveyor: remove verbose mode as output is truncated, and I can't see what's wrong 7 years ago
checkpoint.go move packer to hashicorp 9 years ago
commands.go implement a packer console analogous to the terraform console 7 years ago
config.go use port as ints 7 years ago
go.mod chore: go modules integration 7 years ago
go.sum chore: go modules integration 7 years ago
log.go Use Sprint() instead of Sprintf() in log dedupe 7 years ago
main.go allow building packer on solaris by removing progress bar and tty imports 7 years ago
main_test.go move packer to hashicorp 9 years ago
panic.go Add telemetry reporting through checkpoint 9 years ago
tty.go allow building packer on solaris by removing progress bar and tty imports 7 years ago
tty_solaris.go allow building packer on solaris by removing progress bar and tty imports 7 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.