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
Adrien Delorme a204a14973
Update question.md
7 years ago
.circleci
.github Update question.md 7 years ago
builder Merge pull request #8106 from shapeblue-br/master 7 years ago
command
common common: fix dropped errors and warnings in test 7 years ago
communicator fixup: Propagate bind errors up 7 years ago
contrib
examples Clarify sysprep log message in Azure example 7 years ago
fix
helper SSH tunneling support 7 years ago
packer remove any reference to Push 7 years ago
plugin/example
post-processor Merge pull request #8097 from onematchfox/vagrant-cloud 7 years ago
provisioner
scripts
template remove any reference to Push 7 years ago
test SSH tunneling support 7 years ago
vendor update yandex-cloud/go-sdk & yandex-cloud/go-genproto 7 years ago
version
website Added disk_block_size unit clarification to hyperv-iso doc 7 years ago
.gitattributes
.gitignore
CHANGELOG.md update changelog 7 years ago
CODEOWNERS
Dockerfile
LICENSE
Makefile go get use enumer@master 7 years ago
README.md
Vagrantfile
checkpoint.go
commands.go
config.go
go.mod update yandex-cloud/go-sdk & yandex-cloud/go-genproto 7 years ago
go.sum update yandex-cloud/go-sdk & yandex-cloud/go-genproto 7 years ago
log.go
main.go
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.