Go to file
Rickard von Essen a2a593759e
Merge pull request #6041 from Xeite/f-add-instance-name
builder/openstack: Add instance_name config to OpenStack builder
2018-04-23 08:47:50 +02:00
.github move contributing doc out of root 2018-04-02 10:52:27 -07:00
builder Merge pull request #6041 from Xeite/f-add-instance-name 2018-04-23 08:47:50 +02:00
command update atlas deprecation language 2018-03-19 10:50:29 -07:00
common fix bug with empty boot command. 2018-04-21 11:40:47 -07:00
communicator remove attempt to discover whether destination is a directory from upload function in various communicators 2018-04-10 08:13:06 -07:00
contrib forces az cli to output in JSON where required 2018-04-16 08:01:31 +10:00
examples add expect_disconnect otherwise the build fails 2018-04-18 12:05:27 -07:00
fix s/boot_command/bootcommand/ 2018-04-19 14:26:31 -07:00
helper Include arch and os 2018-04-05 14:28:50 -04:00
packer spelling: warnings 2018-03-14 03:29:50 +00:00
plugin/example
post-processor s/boot_command/bootcommand/ 2018-04-19 14:26:31 -07:00
provisioner Merge pull request #3891 from nouney/f-generated-files 2018-04-05 16:08:38 -07:00
scripts Better override support for PS build script 2018-03-05 01:58:30 -08:00
template
test
vendor Maximize scancode throughput. 2018-04-19 14:26:29 -07:00
version version 1.2.3 dev 2018-03-26 14:23:07 -07:00
website Merge pull request #6041 from Xeite/f-add-instance-name 2018-04-23 08:47:50 +02:00
.gitattributes
.gitignore
.travis.yml test on go 1.9.x branch, remove 1.7.x from tests 2018-02-16 12:00:33 -08:00
CHANGELOG.md update changelog 2018-04-20 12:23:27 -07:00
CODEOWNERS
LICENSE
Makefile s/boot_command/bootcommand/ 2018-04-19 14:26:31 -07:00
README.md update github link to point to hashicorp 2018-04-02 20:09:32 -07:00
Vagrantfile
appveyor.yml
checkpoint.go
commands.go
config.go
log.go
main.go s/boot_command/bootcommand/ 2018-04-19 14:26:31 -07:00
main_test.go
panic.go
stdin.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

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.