You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
David Dymko e1f70147d9
vultr remote docs (#11070)
1 year ago
.circleci remove codecov from repo (#10955) 1 year ago
.github workflows/issue-comment-created.yml: Add GH token input 1 year ago
acctest add plugin acceptance test using amazon plugin 2 years ago
builder extract oneandone and add remote docs 1 year ago
cmd Use packer-sdc in packer + remove mapstructure-to-hcl2 & struct-markdown (#10913) 1 year ago
command fix: print unchanged formatted file when using stdin (#11047) 1 year ago
contrib/zsh-completion Extract Azure plugin components from Packer (#10979) 1 year ago
datasource Vendor amazon plugin (#10800) 2 years ago
examples Add http_content func to serve variables from HTTP @ preseed (#10801) 2 years ago
fix fix fixer deprecated options conflict 2 years ago
hcl2template fix: print unchanged formatted file when using stdin (#11047) 1 year ago
helper move provisioner acceptance tests into sdk alongside builder acceptance tests. Reorganize slightly to make sure no import cycles of doom get formed 2 years ago
packer Say so when an only or an except option did not match anything (#11050) 1 year ago
post-processor Breakout yandex (#10970) 1 year ago
provisioner Extract Azure plugin components from Packer (#10979) 1 year ago
scripts Add release build for darwin/arm64 (#10804) 2 years ago
test Extract ansible plugins (#10912) 1 year ago
version Putting source back into Dev Mode 2 years ago
website vultr remote docs (#11070) 1 year ago
.gitattributes HCL2: add templatefile function (#10776) 2 years ago
.gitignore Remove the vendor dir (#10916) 1 year ago
.golangci.yml Remove the vendor dir (#10916) 1 year ago
.hashibot.hcl remove hashibot (#11053) 1 year ago
CHANGELOG.md update changelog 1 year ago
CODEOWNERS remove outdatedlinode codeowners (#10957) 1 year ago
Dockerfile Use docker mirror 2 years ago
LICENSE LICENSE: MPL2 9 years ago
Makefile Remove the vendor dir (#10916) 1 year ago
README.md remove codecov from repo (#10955) 1 year ago
Vagrantfile vagrantfile: add support for docker provider 4 years ago
background_check.go surface notimplemented errs too 3 years ago
background_check_openbsd.go copypasta 3 years ago
checkpoint.go remove sdk 2 years ago
commands.go HCL2 Parse packer.required_plugins block + packer init (#10304) 2 years ago
config.go HCL2 Parse packer.required_plugins block + packer init (#10304) 2 years ago
config_test.go HCL2 Parse packer.required_plugins block + packer init (#10304) 2 years ago
go.mod vendor oneandone 1 year ago
go.sum vendor oneandone 1 year ago
log.go log errors in scanner and manually close logging pipe if we hit an error in the scanner 3 years ago
main.go add massive warning about error logging to WrappedMain 2 years ago
main_test.go move packer to hashicorp 6 years ago
mlc_config.json Fix markdown link checker issues (#10575) 2 years ago
panic.go Add telemetry reporting through checkpoint 5 years ago
tty.go allow building packer on solaris by removing progress bar and tty imports 3 years ago
tty_solaris.go remove sdk 2 years ago

README.md

Packer

Build Status Discuss PkgGoDev GoReportCard

HashiCorp Packer logo

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.

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.pkr.hcl. Export your AWS credentials as the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.

variable "access_key" {
  type    = string
  default = "${env("AWS_ACCESS_KEY_ID")}"
}

variable "secret_key" {
  type    = string
  default = "${env("AWS_SECRET_ACCESS_KEY")}"
}

locals { timestamp = regex_replace(timestamp(), "[- TZ:]", "") }

source "amazon-ebs" "quick-start" {
  access_key    = "${var.access_key}"
  ami_name      = "packer-example ${local.timestamp}"
  instance_type = "t2.micro"
  region        = "us-east-1"
  secret_key    = "${var.secret_key}"
  source_ami    = "ami-af22d9b9"
  ssh_username  = "ubuntu"
}

build {
  sources = ["source.amazon-ebs.quick-start"]
}

Next, tell Packer to build the image:

$ packer build quick-start.pkr.hcl
...

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 at https://www.packer.io/docs.

Contributing to Packer

See CONTRIBUTING.md for best practices and instructions on setting up your development environment to work on Packer.

Unmaintained Plugins

As contributors' circumstances change, development on a community maintained plugin can slow. When this happens, the Packer team may mark a plugin as unmaintained, to clearly signal the plugin's status to users.

What does unmaintained mean?

  1. The code repository and all commit history will still be available.
  2. Documentation will remain on the Packer website.
  3. Issues and pull requests are monitored as a best effort.
  4. No active development will be performed by the Packer team.

If anyone form them community is interested in maintaining a community supported plugin, please feel free to submit contributions via a pull- request for review; reviews are generally prioritized over feature work when possible. For a list of open plugin issues and pending feature requests see the Packer Issue Tracker.