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
Matthew Hooker e4bd30e53d
fix bug with empty boot command.
8 years ago
.github move contributing doc out of root 8 years ago
builder Merge pull request #6039 from stack72/triton-insecure-skip-tls-verify 8 years ago
command update atlas deprecation language 8 years ago
common fix bug with empty boot command. 8 years ago
communicator remove attempt to discover whether destination is a directory from upload function in various communicators 8 years ago
contrib forces az cli to output in JSON where required 8 years ago
examples add expect_disconnect otherwise the build fails 8 years ago
fix s/boot_command/bootcommand/ 8 years ago
helper Include arch and os 8 years ago
packer spelling: warnings 8 years ago
plugin/example delete unneeded plugin file 9 years ago
post-processor s/boot_command/bootcommand/ 8 years ago
provisioner Merge pull request #3891 from nouney/f-generated-files 8 years ago
scripts Better override support for PS build script 8 years ago
template Add new `packer_version` function. 8 years ago
test Add options to LXC builder for influencing for how containers are built and started 8 years ago
vendor Maximize scancode throughput. 8 years ago
version version 1.2.3 dev 8 years ago
website Merge pull request #6039 from stack72/triton-insecure-skip-tls-verify 8 years ago
.gitattributes On windows a lot of git clients will convert LF to CRLF. This would be a problem where file contents are compared exactly 9 years ago
.gitignore Merge pull request #5206 from sandersaares/hyperv-second-temp-dir 8 years ago
.travis.yml test on go 1.9.x branch, remove 1.7.x from tests 8 years ago
CHANGELOG.md update changelog 8 years ago
CODEOWNERS add scaleway codeowners 8 years ago
LICENSE LICENSE: MPL2 13 years ago
Makefile s/boot_command/bootcommand/ 8 years ago
README.md update github link to point to hashicorp 8 years ago
Vagrantfile [vagrant] Remove redundant configuration block. 8 years ago
appveyor.yml fix appveyor 9 years ago
checkpoint.go move packer to hashicorp 9 years ago
commands.go Re-factor version command to use version.FormattedVersion() function. 8 years ago
config.go move packer to hashicorp 9 years ago
log.go Fix debug logging 10 years ago
main.go s/boot_command/bootcommand/ 8 years ago
main_test.go move packer to hashicorp 9 years ago
panic.go Add telemetry reporting through checkpoint 9 years ago
stdin.go Gracefully clean up on SIGTERM 9 years ago

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

Download and install packages and dependencies

go get github.com/hashicorp/packer

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.