user avatar
5da5b00e
Name Last commit Last update
.circleci pin to go 1.13 & cleanup go deps
.github Document how code generation works a little in .github/CONTRIBUTING.md
builder [builder/openstack] adds option to discover provisioning network
cmd when using a slice of an imported field type, the Underlying still returned the slice rather than the element type.
command Add azure-chroot builder plugin
common Merge pull request #8269 from paulmey/paulmey/generalize-chroot
communicator fixup: Propagate bind errors up
contrib Fix zsh auto-completion
examples Merge pull request #8250 from tencentyun/master
fix Move fixer test to fix package
hcl2template uncomment duplicate check tests
helper commit old code generation tool
packer remote duplicate gob.Register(new(map[string]interface{}))
plugin/example delete unneeded plugin file
post-processor post-processor/compress: fix dropped errors
provisioner commit old code generation tool
scripts change installation of pigeon if off gopath
template improve error message
test SSH tunneling support
vendor [builder/openstack] adds option to discover provisioning network
version update to version 1.5.0-dev
website [builder/openstack] adds option to discover provisioning network
.gitattributes refresh line endings
.gitignore scrape builder docs from https://www.packer.io/docs/
.travis.yml test osx on travis
CHANGELOG.md
CODEOWNERS
Dockerfile
LICENSE
Makefile
README.md
Vagrantfile
appveyor.yml
background_check.go
background_check_openbsd.go
checkpoint.go
commands.go
config.go
go.mod
go.sum
log.go
main.go
main_test.go
panic.go
tty.go
tty_solaris.go

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.