Go to file
Jeff Escalante 3a55b92733
regenerate partials
2020-05-29 17:33:35 -04:00
.circleci
.github
builder patch source for a couple code block changes 2020-05-29 17:22:16 -04:00
cmd HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
command
common HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
communicator
contrib
examples
fix fix fixer 2020-05-28 16:41:00 -07:00
hcl2template HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
helper HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
packer move this to after the prepare() is successful so that we don't try to run builds that didn't prepare successfully. 2020-05-28 11:34:00 -07:00
plugin/example
post-processor HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
provisioner HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
scripts
template HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
test
vendor
version
website regenerate partials 2020-05-29 17:33:35 -04:00
.codecov.yml
.gitattributes
.gitignore
.golangci.yml
.hashibot.hcl
CHANGELOG.md Update CHANGELOG.md 2020-05-28 21:15:17 -07:00
CODEOWNERS
Dockerfile
LICENSE
Makefile
README.md
Vagrantfile
background_check.go
background_check_openbsd.go
checkpoint.go
commands.go
config.go
config_test.go
go.mod
go.sum
log.go
main.go
main_test.go
panic.go
tty.go
tty_solaris.go

README.md

Packer

Build Status Windows Build Status GoDoc GoReportCard codecov

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.