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 a02a95e992
Move port logging to inside of appropriate functions; log the actual plugin being called if it is part of the main packer binary, rather than the meaningless information 'packer'.
6 years ago
.circleci pin to go 1.13 & cleanup go deps 7 years ago
.github Document how code generation works a little in .github/CONTRIBUTING.md 6 years ago
builder Remove unnecessary 1 sec sleep (#8453) 6 years ago
cmd Change back to make sure all durations are a time.Duration 6 years ago
command update ucloud packer 6 years ago
common Fix floppy doc markdown typo (#8458) 6 years ago
communicator fixup: Propagate bind errors up 7 years ago
contrib Fix zsh auto-completion 7 years ago
examples update bucket about no create 6 years ago
fix Implement fixer to convert qemu disk size type to string 6 years ago
hcl2template Force durations to be passed a strings 6 years ago
helper helper/communicator/step_connect_ssh: Update proxy connection settings to use `SSHProxyUsername` and `SSHProxyPassword` 6 years ago
packer Move port logging to inside of appropriate functions; log the actual plugin being called if it is part of the main packer binary, rather than the meaningless information 'packer'. 6 years ago
plugin/example
post-processor post-processor/docker-push: drop unused test helper functions (#8456) 6 years ago
provisioner use shell struct in shell-local provisioner and post-processor. 6 years ago
scripts scripts: close file after error handling 6 years ago
template Change back to make sure all durations are a time.Duration 6 years ago
test test: Generalize README to avoid AWS 6 years ago
vendor builder/hyperone: fix & add tests for tags 6 years ago
version Update version.go 6 years ago
website Fix floppy doc markdown typo (#8458) 6 years ago
.gitattributes refresh line endings 7 years ago
.gitignore scrape builder docs from https://www.packer.io/docs/ 7 years ago
.travis.yml test osx on travis 7 years ago
CHANGELOG.md update changelog 6 years ago
CODEOWNERS fix docs index 6 years ago
Dockerfile dockerfile: add minimal image with provisioners support 7 years ago
LICENSE
Makefile Update Makefile 6 years ago
README.md
Vagrantfile vagrantfile: add support for docker provider 7 years ago
appveyor.yml remove appveyor and travis cfg files 7 years ago
background_check.go surface notimplemented errs too 7 years ago
background_check_openbsd.go copypasta 7 years ago
checkpoint.go
commands.go implement a packer console analogous to the terraform console 7 years ago
config.go only log when external plugin is used, since this is the much rarer event 6 years ago
go.mod builder/hyperone: fix & add tests for tags 6 years ago
go.sum builder/hyperone: fix & add tests for tags 6 years ago
log.go log errors in scanner and manually close logging pipe if we hit an error in the scanner 6 years ago
main.go remove timestamps from logger inside of subprocesses to prevent double logging; also remove some cruft and fix spelling in some logs 6 years ago
main_test.go
panic.go
tty.go allow building packer on solaris by removing progress bar and tty imports 7 years ago
tty_solaris.go allow building packer on solaris by removing progress bar and tty imports 7 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

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.