Go to file
Adrien Delorme 14486003a1 fix test to be race free 2019-05-02 15:04:02 +02:00
.circleci circle-ci: build each support GOOS in a separate run using vendors to make this faster 2019-05-01 13:54:24 +02:00
.github Updating to suggested future-proof comment 2019-04-19 01:48:08 +00:00
builder Merge pull request #7553 from hashicorp/fix_7404 2019-05-01 12:13:00 -07:00
command fix test to be race free 2019-05-02 15:04:02 +02:00
common remove trying port log as retry code will show errors 2019-05-01 13:04:51 +02:00
communicator allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
contrib added the ability to limit number of builds running in parallel 2019-04-13 22:31:54 +10:00
examples update alicloud builder to use official SDK (#7477) 2019-04-26 10:37:49 +08:00
fix Merge pull request #7456 from hashicorp/do_5770 2019-04-05 09:12:20 -07:00
helper allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
packer Merge pull request #7583 from hashicorp/update_custom_plugin_docs 2019-04-30 11:58:53 +02:00
plugin/example delete unneeded plugin file 2017-09-28 10:52:54 -07:00
post-processor update alicloud builder to use official SDK (#7477) 2019-04-26 10:37:49 +08:00
provisioner move retry code into the common/retry pkg and make retry context aware 2019-04-09 17:46:38 +02:00
scripts Update build.sh. Remove solaris, add mipsXX and s390x 2019-04-25 16:29:25 -04:00
template allow to set provisioner timeout from buildfile 2019-04-08 20:09:21 +02:00
test Add Linode Images builder 2019-04-15 20:40:59 -04:00
vendor tidy vendors 2019-05-02 11:50:26 +02:00
version update version 2019-04-11 15:25:46 -07:00
website Merge remote-tracking branch 'origin/master' into pr/7501 2019-05-02 11:47:43 +02:00
.gitattributes too many files for shell during Make, convert .go and .sh to EOL=lf 2018-04-07 05:22:39 -04:00
.gitignore switch to netlify deployment 2018-09-19 12:17:28 -07:00
.travis.yml make sure CI builds with GO111MODULE=off 2019-04-11 14:19:25 +02:00
CHANGELOG.md update changelog 2019-04-11 11:17:34 -07:00
CODEOWNERS add linode builder owners 2019-04-16 12:55:55 -04:00
Dockerfile dockerfile: add minimal image with provisioners support 2018-10-31 16:58:06 +03:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile check if running `go mod vendor` has an effect on vendor directory and if so fail 2019-04-11 14:19:25 +02:00
README.md Miscellaneous doc improvements 2018-10-18 19:09:49 -04:00
Vagrantfile vagrantfile: add support for docker provider 2018-10-31 16:58:06 +03:00
appveyor.yml make sure CI builds with GO111MODULE=off 2019-04-11 14:19:25 +02:00
checkpoint.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
commands.go Complete Atlas deprecation. 2018-08-02 20:23:28 -07:00
config.go use port as ints 2019-03-19 15:01:12 +01:00
go.mod Merge pull request #7567 from creack/bump-goselect2 2019-04-30 12:02:31 +02:00
go.sum Merge pull request #7567 from creack/bump-goselect2 2019-04-30 12:02:31 +02:00
log.go Use Sprint() instead of Sprintf() in log dedupe 2018-10-09 22:43:54 -04:00
main.go main.go: don't set TTY interface from tty.Open() in case open fails 2019-04-25 10:48:40 +02: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

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.