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
DanHam 30a71da8e7
Add tests for disk compaction step
8 years ago
.github move contributing doc out of root 8 years ago
builder Add tests for disk compaction step 8 years ago
command Update 'packer fix' command usage output to include all fixers 8 years ago
common Add checks/error reporting to compaction process 8 years ago
communicator make trailing slash still work 8 years ago
contrib forces az cli to output in JSON where required 8 years ago
examples Add ansible connection plugin examples 8 years ago
fix Ensure amazon-private-ip fixes string values 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 refactored env var code and tests so that I don't have to set env vars during tests to check logic 8 years ago
provisioner Merge pull request #6501 from Wenzel/expose_ansible_packer_http_addr 8 years ago
scripts use xargs to check for formatting 8 years ago
template
test
vendor Cut version 1.2.5 8 years ago
version update to version 1.2.6-dev 8 years ago
website Merge pull request #6501 from Wenzel/expose_ansible_packer_http_addr 8 years ago
.gitattributes too many files for shell during Make, convert .go and .sh to EOL=lf 8 years ago
.gitignore ignore Eclipse project files 8 years ago
.travis.yml add back in tests on latest go, but allow it to fail. 8 years ago
CHANGELOG.md final changelog update for v.1.2.5 8 years ago
CODEOWNERS
LICENSE
Makefile Prevent make fmt from failing in default case 8 years ago
README.md Remove `go get` from Quick Start as this isn't required to use Packer 8 years ago
Vagrantfile
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.