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
nywilken 93640b0854
Update test case for Windows
6 years ago
.circleci pin to go 1.13 & cleanup go deps 7 years ago
.github Document how code generation works a little in .github/CONTRIBUTING.md 6 years ago
builder Add retry mechanism to amazon DeleteSnapshot (#8614) 6 years ago
cmd mapstructure-to-hcl2: make basic named types pointers ( optional ) 6 years ago
command remove extraneous files from when vsphere builder was a plugin, and move README into packer website as separated docs for vsphere-clone and vsphere-iso. Move option descriptions into struct code, and generate documentation directly from those structs as we do inside of the other builders 6 years ago
common Share SourceImageName with provisioners and manifest post-processor (#8603) 6 years ago
communicator fixup: Propagate bind errors up 7 years ago
contrib Fix zsh auto-completion 7 years ago
examples update bucket about no create 6 years ago
fix Rename communicator config variables and remove deprecated code (#8584) 6 years ago
hcl2template mapstructure-to-hcl2: make basic named types pointers ( optional ) 6 years ago
helper Share SourceImageName with provisioners and manifest post-processor (#8603) 6 years ago
packer Share SourceImageName with provisioners and manifest post-processor (#8603) 6 years ago
plugin/example delete unneeded plugin file 9 years ago
post-processor Share SourceImageName with provisioners and manifest post-processor (#8603) 6 years ago
provisioner fix winrmpass sanitization to account for empty string value. 6 years ago
scripts scripts/vagrant: Update Vagrant bootstrapping scripts 6 years ago
template add tests for info sharing 6 years ago
test test: Generalize README to avoid AWS 6 years ago
vendor Get plugin up to parity with v1.5.0. Remove custom jetbrains-internal testing logic; disable acceptance tests (for now) until we can set up a test rig inside of HashiCorp. Regenerate code based on vendoring changes. 6 years ago
version update to 1.5.2-dev 6 years ago
website Share SourceImageName with provisioners and manifest post-processor (#8603) 6 years ago
.gitattributes refresh line endings 7 years ago
.gitignore scrape builder docs from https://www.packer.io/docs/ 7 years ago
.travis.yml test osx on travis 7 years ago
CHANGELOG.md Fix regression in docker-tag post-processor (#8593) 6 years ago
CODEOWNERS add @alexyueer to codeowners for alicloud 6 years ago
Dockerfile dockerfile: add minimal image with provisioners support 7 years ago
LICENSE
Makefile Update Makefile 6 years ago
README.md Miscellaneous doc improvements 7 years ago
Vagrantfile vagrantfile: add support for docker provider 7 years ago
appveyor.yml remove appveyor and travis cfg files 7 years ago
background_check.go surface notimplemented errs too 7 years ago
background_check_openbsd.go copypasta 7 years ago
checkpoint.go
commands.go implement a packer console analogous to the terraform console 7 years ago
config.go config: Update loading of packerconfig to only log when a plugin is loaded 6 years ago
config_test.go Update test case for Windows 6 years ago
go.mod Get plugin up to parity with v1.5.0. Remove custom jetbrains-internal testing logic; disable acceptance tests (for now) until we can set up a test rig inside of HashiCorp. Regenerate code based on vendoring changes. 6 years ago
go.sum Get plugin up to parity with v1.5.0. Remove custom jetbrains-internal testing logic; disable acceptance tests (for now) until we can set up a test rig inside of HashiCorp. Regenerate code based on vendoring changes. 6 years ago
log.go log errors in scanner and manually close logging pipe if we hit an error in the scanner 6 years ago
main.go config: Fix loading external plugins from a packerconfig 6 years ago
main_test.go
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.