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
Megan Marsh e2283445f2
need to initialize variables scoped to the individual loop, because the address of k,v stay the same and that means we overwrite previous variables when assigning them to the struct directly.
6 years ago
.circleci
.github Create ssh_or_winrm_times_out.md 6 years ago
builder need to initialize variables scoped to the individual loop, because the address of k,v stay the same and that means we overwrite previous variables when assigning them to the struct directly. 6 years ago
cmd when using a slice of an imported field type, the Underlying still returned the slice rather than the element type. 6 years ago
command Add azure-chroot builder plugin 6 years ago
common Merge pull request #8269 from paulmey/paulmey/generalize-chroot 6 years ago
communicator
contrib
examples Merge pull request #8250 from tencentyun/master 6 years ago
fix
hcl2template uncomment duplicate check tests 6 years ago
helper commit old code generation tool 6 years ago
packer remote duplicate gob.Register(new(map[string]interface{})) 6 years ago
plugin/example
post-processor commit old code generation tool 6 years ago
provisioner commit old code generation tool 6 years ago
scripts
template improve error message 6 years ago
test
vendor Revert "vendor vendors" 6 years ago
version
website Merge pull request #8246 from hashicorp/fix_8089 6 years ago
.gitattributes
.gitignore
.travis.yml
CHANGELOG.md proxmos -> proxmox 6 years ago
CODEOWNERS Add builder CODEOWNERS to respective docs 6 years ago
Dockerfile
LICENSE
Makefile Update Makefile 6 years ago
README.md
Vagrantfile
appveyor.yml
background_check.go
background_check_openbsd.go
checkpoint.go
commands.go
config.go
go.mod Revert "vendor vendors" 6 years ago
go.sum Revert "vendor vendors" 6 years ago
log.go
main.go
main_test.go
panic.go
tty.go
tty_solaris.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.