Packer - Build d'images (VMs, containers, ISOs)
Find a file
hc-github-team-packer c9bfbc699c
bump golang.org/x/crypto to 0.43.0 (#13518) (#13529)
* bump golang.org/x/crypto to 0.43.0
CVE-2025-47913 GO-2025-4116

* fixed go.sum

* fixed multiple warnings that prevented test runs

* make generate

* fix lint errors, update linter version

* fix go vet issues

Co-authored-by: Anurag Sharma <36436571+anurag5sh@users.noreply.github.com>
2025-11-18 18:35:05 +05:30
.github bump backport-assistant to 0.5.8 (#13471) (#13522) 2025-11-18 18:33:17 +05:30
.release backport of commit 6d2f7ad396 (#13526) 2025-11-18 17:39:56 +05:30
acctest packer: relax constraints on sources 2024-04-29 14:28:24 -04:00
builder packer: address unused lint errors 2024-07-18 10:51:17 -04:00
cmd chore: remove refs to deprecated io/ioutil 2023-09-26 11:13:31 -04:00
command backport of commit 3cb0cd490e (#13525) 2025-11-18 17:39:28 +05:30
contrib/zsh-completion Update fix command autocomplete to work for JSON template files only (#12366) 2023-04-14 13:00:24 -04:00
datasource bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
examples Fixes typos in docs (#11322) 2021-10-11 10:19:49 +02:00
fix packer: address gosimple lint errors 2024-07-18 10:51:17 -04:00
hcl2template bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
helper backport of commit 3cb0cd490e (#13525) 2025-11-18 17:39:28 +05:30
internal bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
packer bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
packer_test bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
post-processor packer: address unused lint errors 2024-07-18 10:51:17 -04:00
provisioner bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
scripts Adding darwin/386 as part of unsupported GOOS/GOARCH pair. 2025-02-20 11:43:28 -05:00
version backport of commit 5580ca2338 (#13521) 2025-11-18 17:37:26 +05:30
website bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
.copywrite.hcl update year in license files 2023-12-06 12:43:42 -08:00
.gitattributes HCL2: add templatefile function (#10776) 2021-03-23 12:02:05 +01:00
.gitignore Remove the vendor dir (#10916) 2021-04-21 10:52:55 +02:00
.go-version .go-version: bump to 1.23.2 2025-03-06 15:07:46 -05:00
.golangci.yml golangci.yml: add rule to not run errcheck on test 2024-07-18 10:51:17 -04:00
background_check.go [COMPLIANCE] License changes (#12568) 2023-08-10 15:53:29 -07:00
background_check_openbsd.go [COMPLIANCE] License changes (#12568) 2023-08-10 15:53:29 -07:00
CHANGELOG.md Changelog update to include sdk changes (#13468) 2025-09-09 16:00:40 +05:30
checkpoint.go [COMPLIANCE] License changes (#12568) 2023-08-10 15:53:29 -07:00
CODEOWNERS add access to redirects and readme 2025-02-06 10:32:32 -08:00
commands.go commands: introduce plugin as alias to plugins 2024-03-11 15:06:13 -04:00
config.go packer: pick protobuf/gob for serialisation (#13025) 2025-01-21 16:44:03 -05:00
config_test.go config: rm mono-component support from config file (#12998) 2024-05-30 14:25:08 +02:00
Dockerfile Dockerfile: Add Product directory to /usr/share/doc directory 2024-04-23 09:28:35 -04:00
go Bump Go tooling version to 1.20.8 2023-10-03 10:32:42 -04:00
go.mod bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
go.sum bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
LICENSE update year in license files 2023-12-06 12:43:42 -08:00
log.go bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
main.go backport of commit 3cb0cd490e (#13525) 2025-11-18 17:39:28 +05:30
main_test.go [COMPLIANCE] License changes (#12568) 2023-08-10 15:53:29 -07:00
Makefile bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
panic.go bump golang.org/x/crypto to 0.43.0 (#13518) (#13529) 2025-11-18 18:35:05 +05:30
README.md Update README 2023-10-26 15:03:55 -04:00
tty.go [COMPLIANCE] License changes (#12568) 2023-08-10 15:53:29 -07:00
tty_solaris.go [COMPLIANCE] License changes (#12568) 2023-08-10 15:53:29 -07:00
Vagrantfile vagrantfile: add support for docker provider 2018-10-31 16:58:06 +03:00

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.