Aidan Feldman b894c925d1 make user retrieval for Ansible provisioner more robust
Previously, the Ansible provisioner would look for the username from the
`USER` environment variable. Unfortunately, this is not always set -
particularly in Docker containers. It's very confusing to understand why
the error is happening.

Switched to using Go's built-in `os/user` package for retrieving the
current username. @rickard-von-essen had done this in 7369841, but
moved away from it in d59844f because, at the time, it wasn't possible
to use that library with cross-compilation. This was fixed in Go in

https://github.com/golang/go/commit/795e712b72802ad49b7c077964046f79c4f6586e
2018-01-03 02:52:41 -05:00
2017-06-28 07:39:26 +02:00
2017-10-10 15:04:15 +01:00
2017-08-03 23:11:52 +02:00
2017-10-25 10:53:06 -07:00
2017-11-30 16:30:37 -08:00
2017-12-19 11:32:33 -08:00
2017-11-21 22:04:33 +01:00
2017-12-08 15:45:12 -08:00
2017-06-06 11:52:21 -07:00
2017-12-29 13:34:05 -06:00
2017-04-04 13:39:01 -07:00
2017-10-30 12:51:22 -07:00
2017-04-04 13:39:01 -07:00
2013-06-24 14:29:15 -07:00
2016-10-07 21:10:20 +02:00
2017-04-04 13:39:01 -07:00
2017-10-23 12:10:31 -07:00

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.

S
Description
No description provided
Readme
163 MiB
Languages
Go 94.2%
HCL 4%
Shell 0.8%
Makefile 0.3%
MDX 0.3%
Other 0.4%