Go to file
SwampDragons 074ddbea8e
Merge pull request #5732 from KohlsTechnology/vagrant_google
Add vagrant post-processor support for Google
2018-01-31 15:49:02 -08:00
.github Updated ISSUE_TEMPLATE.md 2017-06-28 07:39:26 +02:00
builder use helper functions for reading vmx files 2018-01-31 13:19:31 -08:00
command trying to add context to state bag 2018-01-24 17:09:15 -08:00
common test fixes WIP 2018-01-24 17:09:17 -08:00
communicator ssh deadlines 2018-01-31 12:35:25 -08:00
contrib Update _packer 2017-08-03 23:11:52 +02:00
examples remove obsolete ssh_wait_timeout from examples 2018-01-30 23:30:45 -08:00
fix run goimports 2018-01-22 17:21:10 -08:00
helper ssh deadlines 2018-01-31 12:35:25 -08:00
packer run goimports 2018-01-22 17:21:10 -08:00
plugin/example delete unneeded plugin file 2017-09-28 10:52:54 -07:00
post-processor Merge pull request #5732 from KohlsTechnology/vagrant_google 2018-01-31 15:49:02 -08:00
provisioner tests and docs for #5831 2018-01-31 13:08:25 -08:00
scripts build: Allow multi-platform dev with Vagrantfile 2017-11-02 11:00:19 -07:00
template Add new `packer_version` function. 2017-11-21 22:04:33 +01:00
test Add options to LXC builder for influencing for how containers are built and started 2017-10-30 21:48:43 -04:00
vendor update context library 2018-01-24 17:09:18 -08:00
version prepare for next version 2017-12-08 15:45:12 -08:00
website Merge pull request #5732 from KohlsTechnology/vagrant_google 2018-01-31 15:49:02 -08:00
.gitattributes On windows a lot of git clients will convert LF to CRLF. This would be a problem where file contents are compared exactly 2016-12-12 22:44:50 +00:00
.gitignore Merge pull request #5206 from sandersaares/hyperv-second-temp-dir 2017-10-09 10:08:00 -07:00
.travis.yml travis: update 1.7 and 1.8 go versions 2017-12-20 15:36:02 +01:00
CHANGELOG.md update changelog 2018-01-12 15:11:50 -08:00
CODEOWNERS codeowners for post-processors 2017-10-30 12:51:22 -07:00
CONTRIBUTING.md make examples copy/pastable 2018-01-23 14:34:40 -08:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile Merge pull request #5082 from nak3/makefile-copy-binary 2017-10-13 14:40:15 -07:00
README.md use correct oracle builder name 2017-10-23 12:10:31 -07:00
Vagrantfile [vagrant] Remove redundant configuration block. 2018-01-18 04:34:14 -05:00
appveyor.yml fix appveyor 2017-06-06 11:52:21 -07:00
azure-merge.sh Added merge script to automatically pull in and fix the upstream repo 2016-03-14 20:08:12 -07:00
checkpoint.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
commands.go Re-factor version command to use version.FormattedVersion() function. 2017-12-03 23:07:16 +01:00
config.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
log.go Fix debug logging 2016-10-07 21:10:20 +02:00
main.go log when loading config from environment 2017-12-14 11:26:09 -08:00
main_test.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
panic.go Add telemetry reporting through checkpoint 2017-06-15 13:21:11 -07:00
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 2013-07-25 23:27:13 -07:00

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 the following platforms:

  • Amazon EC2 (AMI). Both EBS-backed and instance-store AMIs
  • Azure
  • CloudStack
  • DigitalOcean
  • Docker
  • Google Compute Engine
  • Hyper-V
  • 1&1
  • OpenStack
  • Oracle Cloud Infrastructure
  • Parallels
  • ProfitBricks
  • QEMU. Both KVM and Xen images.
  • Triton (Joyent Public Cloud)
  • VMware
  • VirtualBox

Support for other platforms can be added via plugins.

The images that Packer creates can easily be turned into Vagrant boxes.

Quick Start

Download and install packages and dependencies

go get github.com/hashicorp/packer

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.