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
Martin Grogan 032ee5af4d
Merge pull request #13293 from sbraz/hcl2_upgrade_command
1 year ago
.github
.release
acctest
builder
cmd
command command: exit non-zero if uploading to HCP failed 1 year ago
contrib/zsh-completion
datasource
examples
fix
hcl2template packer: add hcp-sbom provisioner 1 year ago
helper
internal Ensure org ID is set and move UploadSbom to api package 1 year ago
packer hcp: use enum for HCP SBOM upload 1 year ago
packer_test packer_test: add integration tests for hcp-sbom 1 year ago
post-processor
provisioner website: add docs for the hcp-sbom provisioner 1 year ago
scripts packer: pick protobuf/gob for serialisation (#13025) 1 year ago
version
website website: fix repeated word in link to hcl2_upgrade command doc 1 year ago
.copywrite.hcl
.gitattributes
.gitignore
.go-version
.golangci.yml
CHANGELOG.md CHANGELOG: add changes for v1.12.0 1 year ago
CODEOWNERS add access to redirects and readme 1 year ago
Dockerfile
LICENSE
Makefile
README.md
Vagrantfile
background_check.go
background_check_openbsd.go
checkpoint.go
commands.go
config.go packer: pick protobuf/gob for serialisation (#13025) 1 year ago
config_test.go
go
go.mod build(deps): bump github.com/hashicorp/hcp-sdk-go 1 year ago
go.sum build(deps): bump github.com/hashicorp/hcp-sdk-go 1 year ago
log.go
main.go
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.