Go to file
Tom Dyas c0a6623ea2
teach HCL mode builds to honor -only and -except options (#8947)
2020-04-28 15:03:24 +02:00
.circleci Add RetriedProvisioner to allow retry provisioners (#9061) 2020-04-16 11:58:54 +02:00
.github Merge pull request #9006 from hashicorp/provisioner_acc_contributing 2020-04-07 16:02:16 -07:00
builder fix issue where -force is not working with vsphere builders (#9039) 2020-04-23 08:07:07 -04:00
cmd make docs a bit more readable for KeyValues too 2020-04-21 12:22:37 +02:00
command teach HCL mode builds to honor -only and -except options (#8947) 2020-04-28 15:03:24 +02:00
common HCL2: when we see a map generate an attribute spec instead of a block spec (#9035) 2020-04-14 16:05:13 +02:00
communicator packer.io prefix removal, html extension remove for in-code errors 2020-04-07 17:53:22 -04: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 teach HCL mode builds to honor -only and -except options (#8947) 2020-04-28 15:03:24 +02:00
helper golang 1.14 doesn't like calling NewFile on existing files. Port solution over from Terraform 2020-04-09 14:38:17 -07:00
packer Add RetriedProvisioner to allow retry provisioners (#9061) 2020-04-16 11:58:54 +02:00
plugin/example Add golangci-lint to project (#8686) 2020-02-14 11:42:29 -05:00
post-processor make sure keyvalue and namevalue filters are using the same naming as the service being used 2020-04-16 17:22:13 +02:00
provisioner provisioner/windows-shell: remove unused testObjects() (#9116) 2020-04-27 10:50:31 +02:00
scripts scripts/build: Remove unsupported Freebsd/arm builds from build chain 2020-04-16 06:05:34 -04:00
template Clean linting issues for packages template and interpolate (#9120) 2020-04-27 10:35:47 +02:00
test test: Generalize README to avoid AWS 2019-12-03 14:57:41 +01:00
vendor [builder/azure-chroot] Shared image source (#9070) 2020-04-23 11:03:17 +02:00
version update to v1.5.6-dev 2020-03-25 16:04:05 -07:00
website HCL2: docs warn about the fact that HCL2 support is still Beta at the top of each docs page (#9113) 2020-04-28 11:37:50 +02:00
.codecov.yml Add after_n_builds to codecov.yml (#8913) 2020-03-19 13:18:03 +01:00
.gitattributes clean up documentation for new NIC and storage params 2020-04-13 14:28:50 -04: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-27 14:48:45 +02:00
CODEOWNERS add Hakujou as outscale code owner 2020-04-24 11:55:08 -07: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 Revert golangci-lint to use new-from-rev pinned at 1.23.8 (#9072) 2020-04-15 06:53:51 -04: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
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 teach HCL mode builds to honor -only and -except options (#8947) 2020-04-28 15:03:24 +02:00
go.sum Merge pull request #9104 from hashicorp/up_oci_sdk 2020-04-22 15:04:18 -04: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.