Go to file
Megan Marsh 904c4b9adb
Merge pull request #7230 from hashicorp/up-aws-sdk-go
Don't try to guess region from metadata if not set + update aws-sdk-go
2019-01-25 10:06:11 -08:00
.circleci
.github update contributing guidelines and make sure that the PR template links to them. 2019-01-23 11:35:50 -08:00
builder Merge pull request #7230 from hashicorp/up-aws-sdk-go 2019-01-25 10:06:11 -08:00
command break a chain of post-processors when one is skipped & make `-only` 2019-01-11 14:08:30 +01:00
common If checksums for a download don't match, display the checksum that was found 2019-01-17 20:26:16 +00:00
communicator
contrib Document --except & --only flags for post-processors 2019-01-11 13:00:10 +01:00
examples azure: sysprep after agent is ready 2019-01-08 10:17:33 -08:00
fix
helper
packer break a chain of post-processors when one is skipped & make `-only` 2019-01-11 14:08:30 +01:00
plugin/example
post-processor googlecompute-import: add guest os features 2019-01-22 18:42:38 +01:00
provisioner Merge branch 'master' into pr/6950 2019-01-09 10:11:18 +01:00
scripts
template allow to skip a post processor 2019-01-10 15:44:34 +01:00
test
vendor Revert "debug should retry" 2019-01-24 16:44:53 +01:00
version
website Merge pull request #7156 from vtolstov/qemu 2019-01-23 15:19:08 -08:00
.gitattributes
.gitignore
.travis.yml
CHANGELOG.md update changelog 2019-01-23 14:10:24 -08:00
CODEOWNERS
Dockerfile
LICENSE
Makefile Revert "enable verbose mode to see debug" 2019-01-24 16:44:51 +01:00
README.md
Vagrantfile
appveyor.yml appveyor.yml: timeout tests after 2m 2019-01-24 14:01:23 +01:00
checkpoint.go
commands.go
config.go
go.mod GO111MODULE=on go get github.com/aws/aws-sdk-go@v1.16.24 2019-01-24 13:07:34 +01:00
go.sum GO111MODULE=on go get github.com/aws/aws-sdk-go@v1.16.24 2019-01-24 13:07:34 +01:00
log.go
main.go
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

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.