Go to file
Megan Marsh a7be0bed30 Make Vagrant driver code pass through logs as it receives them rather than buffering and returning them all at the end of the call. 2019-10-24 13:12:35 -07:00
.circleci
.github
builder Make Vagrant driver code pass through logs as it receives them rather than buffering and returning them all at the end of the call. 2019-10-24 13:12:35 -07:00
cmd Update mapstructure-to-hcl2.go 2019-10-16 10:49:20 +02:00
command Add azure-chroot builder plugin 2019-10-15 21:13:37 +00:00
common common: collect dropped error 2019-10-23 13:02:08 -07:00
communicator
contrib
examples Merge pull request #8250 from tencentyun/master 2019-10-21 14:45:37 -07:00
fix
hcl2template uncomment duplicate check tests 2019-10-16 10:37:26 +02:00
helper
packer remote duplicate gob.Register(new(map[string]interface{})) 2019-10-15 12:56:42 +02:00
plugin/example
post-processor
provisioner
scripts
template improve error message 2019-10-23 12:02:31 -07:00
test
vendor Merge pull request #8232 from hashicorp/artifact-tree 2019-10-22 11:54:34 -07:00
version
website remove vnc config options from virtualbox docs; virtualbox does not implement the vncconfig struct 2019-10-22 12:11:27 -07:00
.gitattributes
.gitignore
.travis.yml
CHANGELOG.md proxmos -> proxmox 2019-10-22 19:20:14 +05:30
CODEOWNERS
Dockerfile
LICENSE
Makefile Update Makefile 2019-10-16 10:24:34 +02:00
README.md
Vagrantfile
appveyor.yml
background_check.go
background_check_openbsd.go
checkpoint.go
commands.go
config.go
go.mod Merge pull request #8232 from hashicorp/artifact-tree 2019-10-22 11:54:34 -07:00
go.sum Merge pull request #8232 from hashicorp/artifact-tree 2019-10-22 11:54:34 -07:00
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.