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 e57004b2ec
Merge pull request #8662 from hashicorp/return_with_ssh_wait_timeout
7 years ago
.circleci
.github
builder Merge pull request #8662 from hashicorp/return_with_ssh_wait_timeout 7 years ago
cmd mapstructure-to-hcl2: make basic named types pointers ( optional ) 7 years ago
command remove extraneous files from when vsphere builder was a plugin, and move README into packer website as separated docs for vsphere-clone and vsphere-iso. Move option descriptions into struct code, and generate documentation directly from those structs as we do inside of the other builders 7 years ago
common Extract http ip discover to a new step 7 years ago
communicator
contrib
examples
fix Rename communicator config variables and remove deprecated code (#8584) 7 years ago
hcl2template hcl2: allow to optionnaly name provisioners and post-processors 7 years ago
helper Share SourceImageName with provisioners and manifest post-processor (#8603) 7 years ago
packer Merge pull request #8654 from hashicorp/fix_8583 7 years ago
plugin/example
post-processor Share SourceImageName with provisioners and manifest post-processor (#8603) 7 years ago
provisioner Add packer.ExpandUser() function to support tilde in usage of config.ValidationKeyPath (#8657) 7 years ago
scripts scripts/vagrant: Update Vagrant bootstrapping scripts 7 years ago
template Interpolate boot_command when defined by user variable (#8640) 7 years ago
test test: Generalize README to avoid AWS 7 years ago
vendor Bump proxmox-api-go 7 years ago
version update to 1.5.2-dev 7 years ago
website Merge pull request #8654 from hashicorp/fix_8583 7 years ago
.gitattributes
.gitignore
.hashibot.hcl Update .hashibot.hcl 7 years ago
.travis.yml
CHANGELOG.md update changelog 7 years ago
CODEOWNERS add @alexyueer to codeowners for alicloud 7 years ago
Dockerfile
LICENSE
Makefile
README.md
Vagrantfile
appveyor.yml
background_check.go
background_check_openbsd.go
checkpoint.go
commands.go
config.go config: Update loading of packerconfig to only log when a plugin is loaded 7 years ago
config_test.go Update test case for Windows 7 years ago
go.mod Bump proxmox-api-go 7 years ago
go.sum Bump proxmox-api-go 7 years ago
log.go
main.go config: Fix loading external plugins from a packerconfig 7 years ago
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.