Go to file
Moss 25b91aa3cb Update CONTRIBUTING with ajustments 2020-04-06 18:22:34 +02:00
.circleci Rename codecov.yml to .codecov.yml 2020-03-12 18:43:58 +01:00
.github Update CONTRIBUTING with ajustments 2020-04-06 18:22:34 +02:00
builder Merge pull request #8987 from VaijanathB/azure-devtestlabs-take2 2020-04-03 11:14:31 -07:00
cmd better type for []NameValue in docs 2020-03-17 15:02:04 +01:00
command Fixing the linting errors now required for merging 2020-04-02 17:22:16 -07:00
common move proxy behind feature flag 2020-04-01 11:31:48 -07:00
communicator write unit test 2020-03-13 14:01:11 +09:00
contrib Fix zsh auto-completion 2019-09-26 12:13:02 +01:00
examples update bucket about no create 2019-10-29 16:11:43 -07:00
fix Fix gosimple S1005 linting issue (#8870) 2020-03-11 10:30:08 +01:00
hcl2template make sure locals are evaluated only once variables are + test this (#8918) 2020-03-19 15:30:34 +01:00
helper Write generic Builder-Provisioner acceptance test logic (#8963) 2020-04-03 18:17:09 +02:00
packer Merge pull request #8875 from hashicorp/fix_8812 2020-03-13 12:52:17 -07:00
plugin/example Add golangci-lint to project (#8686) 2020-02-14 11:42:29 -05:00
post-processor Merge pull request #8679 from kwibus/gcp-fallback-image 2020-04-02 16:49:50 -07:00
provisioner Merge pull request #8987 from VaijanathB/azure-devtestlabs-take2 2020-04-03 11:14:31 -07:00
scripts scripts/prepare_changelog: Update unescape parenthesis for improved matching 2020-03-27 07:19:49 -04:00
template execute_command in powershell wasn't interpolating build vars properly (#8771) 2020-03-02 04:20:32 -05:00
test test: Generalize README to avoid AWS 2019-12-03 14:57:41 +01:00
vendor Rebasing with origin/master and fixing issues 2020-04-02 18:15:08 -07:00
version update to v1.5.6-dev 2020-03-25 16:04:05 -07:00
website Merge pull request #8987 from VaijanathB/azure-devtestlabs-take2 2020-04-03 11:14:31 -07:00
.codecov.yml Add after_n_builds to codecov.yml (#8913) 2020-03-19 13:18:03 +01:00
.gitattributes add go mod and go sum to gitattributes to fix line endings on windows (#8734) 2020-02-14 11:20:36 +01:00
.gitignore scrape builder docs from https://www.packer.io/docs/ 2019-06-05 16:41:20 +02:00
.golangci.yml Add golangci-lint to project (#8686) 2020-02-14 11:42:29 -05:00
.hashibot.hcl update hashibot config not to comment when locking super old and stale issues 2020-04-03 11:37:34 -07:00
CHANGELOG.md update changelog 2020-04-03 16:47:34 -07:00
CODEOWNERS add @alexyueer to codeowners for alicloud 2020-01-07 12:48:38 -08: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 Write generic Builder-Provisioner acceptance test logic (#8963) 2020-04-03 18:17:09 +02:00
README.md Add Codecov badge and remove report style (#8896) 2020-03-16 15:59:55 +01:00
Vagrantfile vagrantfile: add support for docker provider 2018-10-31 16:58:06 +03:00
appveyor.yml Update appveyor.yml 2019-06-06 18:35:20 +02:00
background_check.go surface notimplemented errs too 2019-09-19 08:57:50 -07:00
background_check_openbsd.go copypasta 2019-09-18 10:54:35 -07:00
checkpoint.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
commands.go implement a packer console analogous to the terraform console 2019-06-05 16:35:22 -07:00
config.go make period stripping more strict so that users can disable provisiners by adding .old or whatever; this is pretty typical convention. 2020-02-13 12:59:47 -08:00
config_test.go Merge pull request #8616 from hashicorp/packer-plugin-path 2020-01-28 12:09:55 -08:00
go.mod Rebasing with origin/master and fixing issues 2020-04-02 18:15:08 -07:00
go.sum Rebasing with origin/master and fixing issues 2020-04-02 18:15:08 -07:00
log.go log errors in scanner and manually close logging pipe if we hit an error in the scanner 2019-11-11 09:20:39 -08:00
main.go config: Fix loading external plugins from a packerconfig 2020-01-15 13:08:30 -05: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
tty.go allow building packer on solaris by removing progress bar and tty imports 2019-05-07 15:58:49 +02:00
tty_solaris.go allow building packer on solaris by removing progress bar and tty imports 2019-05-07 15:58:49 +02:00

README.md

Packer

Build Status Windows Build Status GoDoc GoReportCard codecov

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.