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
Matthew Hooker a3bf2c786a
Use expression sequence generator in tests.
8 years ago
.github move contributing doc out of root 8 years ago
builder Use contexts with amazon waiters. 8 years ago
command update atlas deprecation language 8 years ago
common Use expression sequence generator in tests. 8 years ago
communicator remove attempt to discover whether destination is a directory from upload function in various communicators 8 years ago
contrib forces az cli to output in JSON where required 8 years ago
examples add expect_disconnect otherwise the build fails 8 years ago
fix s/boot_command/bootcommand/ 8 years ago
helper use build name to ensure that winrm password and other shared state is not overwritten if two builders need the password in the same packer run. 8 years ago
packer spelling: warnings 8 years ago
plugin/example
post-processor s/boot_command/bootcommand/ 8 years ago
provisioner use build name to ensure that winrm password and other shared state is not overwritten if two builders need the password in the same packer run. 8 years ago
scripts Better override support for PS build script 8 years ago
template
test
vendor Maximize scancode throughput. 8 years ago
version version 1.2.3 dev 8 years ago
website bring back turbolinks and adjust scripts to match 8 years ago
.gitattributes
.gitignore
.travis.yml
CHANGELOG.md Updated CHANGELOG.md 8 years ago
CODEOWNERS
LICENSE
Makefile s/boot_command/bootcommand/ 8 years ago
README.md update github link to point to hashicorp 8 years ago
Vagrantfile
appveyor.yml
checkpoint.go
commands.go
config.go
log.go
main.go s/boot_command/bootcommand/ 8 years ago
main_test.go
panic.go
stdin.go

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

Download and install packages and dependencies

go get github.com/hashicorp/packer

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.