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
Patrick Double e7fc651f60
First cut at vagrant post-processor for docker
8 years ago
.github
builder Merge pull request #6439 from jbonachera/scaleway-config-bootscript 8 years ago
command Add new post processor googlecompute-import 8 years ago
common Merge pull request #6422 from DanHam/fix-gh-vmsecureboot 8 years ago
communicator Remove redundant error message. 8 years ago
contrib
examples Updated Samples and added a windows quick start as well 8 years ago
fix s/boot_command/bootcommand/ 8 years ago
helper use build name to ensure that winrm password and other shared state is not overwritten if two builders need the password in the same packer run. 8 years ago
packer resolve conflicts; fix to work with hookedprovisioner which has been added since PR was made 8 years ago
plugin/example
post-processor First cut at vagrant post-processor for docker 8 years ago
provisioner Ensure comments are easily readable in a standard terminal 8 years ago
scripts use xargs to check for formatting 8 years ago
template
test
vendor Add new post processor googlecompute-import 8 years ago
version update version to 1.3.0 dev 8 years ago
website Merge pull request #6439 from jbonachera/scaleway-config-bootscript 8 years ago
.gitattributes
.gitignore
.travis.yml add back in tests on latest go, but allow it to fail. 8 years ago
CHANGELOG.md update changelog 8 years ago
CODEOWNERS
LICENSE
Makefile don't send every source file through the shell 8 years ago
README.md Remove `go get` from Quick Start as this isn't required to use Packer 8 years ago
Vagrantfile First cut at vagrant post-processor for docker 8 years ago
appveyor.yml
checkpoint.go
commands.go
config.go
log.go
main.go Merge branch 'master' into f-autocomplete 8 years ago
main_test.go
panic.go
stdin.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.