Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
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.
 
 
 
 
 
 
Go to file
hc-github-team-packer 87f8308fb2
backport of commit 4b470f340c (#13524)
3 months ago
.github adds workflow-dispatch + sets PACKER_ACC_BUILDERS for acceptance tests (#13444) 7 months ago
.release release: ignore AWS SDK vulnerability for release 1 year ago
acctest packer: relax constraints on sources 2 years ago
builder packer: address unused lint errors 2 years ago
cmd
command changes for pulling binary from releases.hashicorp.com (#13431) 7 months ago
contrib/zsh-completion
datasource backport of commit 3e4e380c82 (#13523) 3 months ago
examples
fix packer: address gosimple lint errors 2 years ago
hcl2template hcl2template: fix spacing in error message 6 months ago
helper
internal Fix incorrect Credential file default path in docs (#13447) 6 months ago
packer changes for allowing proxy server to fetch release binaries (#13439) 7 months ago
packer_test build(deps): bump golang.org/x/oauth2 6 months ago
post-processor packer: address unused lint errors 2 years ago
provisioner removing $result from wrapper string (#13451) 6 months ago
scripts Adding darwin/386 as part of unsupported GOOS/GOARCH pair. 1 year ago
version backport of commit 5580ca2338 (#13521) 3 months ago
website Merge pull request #13438 from hashicorp/packer-plugin-release-notice 6 months ago
.copywrite.hcl update year in license files 2 years ago
.gitattributes
.gitignore
.go-version .go-version: bump to 1.23.2 12 months ago
.golangci.yml golangci.yml: add rule to not run errcheck on test 2 years ago
CHANGELOG.md Changelog update to include sdk changes (#13468) 5 months ago
CODEOWNERS add access to redirects and readme 1 year ago
Dockerfile Dockerfile: Add Product directory to /usr/share/doc directory 2 years ago
LICENSE update year in license files 2 years ago
Makefile Makefile: bump golangci-lint to 1.60.1 12 months ago
README.md
Vagrantfile
background_check.go
background_check_openbsd.go
checkpoint.go
commands.go commands: introduce plugin as alias to plugins 2 years ago
config.go packer: pick protobuf/gob for serialisation (#13025) 1 year ago
config_test.go config: rm mono-component support from config file (#12998) 2 years ago
go
go.mod backport of commit 4b470f340c (#13524) 3 months ago
go.sum backport of commit 4b470f340c (#13524) 3 months ago
log.go log: simplify the logOutput function 2 years ago
main.go packer: address errcheck lint errors 2 years ago
main_test.go
panic.go
tty.go
tty_solaris.go

README.md

Packer

License: BUSL-1.1 Build Status Discuss

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 supports various platforms through external plugin integrations, the full list of which can be found at https://developer.hashicorp.com/packer/integrations.

The images that Packer creates can easily be turned into Vagrant boxes.

Quick Start

Packer

There is a great introduction and getting started guide for building a Docker image on your local machine without using any paid cloud resources.

Alternatively, you can refer to getting started with AWS to learn how to build a machine image for an external cloud provider.

HCP Packer

HCP Packer registry stores Packer image metadata, enabling you to track your image lifecycle.

To get started with building an AWS machine image to HCP Packer for referencing in Terraform refer to the collection of HCP Packer Tutorials.

Documentation

Comprehensive documentation is viewable on the Packer website at https://developer.hashicorp.com/packer/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, HashiCorp may use GitHub's option to archive the plugins repository, 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 HashiCorp.

If you are interested in maintaining an unmaintained or archived plugin, please reach out to us at packer@hashicorp.com.