OSS TanbouSign in with GitHub

build reproducible machine images for multiple platforms from one HCL configuration

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
15,809
Primary language
Go
License
BUSL-1.1
Repository last updated
Oct 4, 2026
On this page

Overview

Packer automates machine-image creation from a single source configuration for targets such as cloud VM images and other platform artifacts. Builders, provisioners, and post-processors are composed through plugins so the same application baseline can be produced across multiple environments.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Define machine-image builds in HCL

Packer source, build, and provisioning behavior can be declared as configuration so platform-specific image workflows remain repeatable and reviewable.

Sources: [1]

Extend cloud and virtualization support through external plugins

Provider integrations are distributed as external plugins. Version 1.16.1 expands plugin installation to non-GitHub HTTPS sources such as mirrors and artifact repositories that use the HashiCorp release layout.

Sources: [1][2]

Produce images for multiple platforms from the same source in parallel

Packer is designed to build identical machine images for multiple platforms from one source configuration and can execute platform builds in parallel.

Sources: [1]

Best fit

Fits immutable-infrastructure and golden-image pipelines managed as code

It is useful when platform teams want CI/CD to repeatedly produce a known image baseline and pass those artifacts into provisioning systems such as Terraform rather than maintaining servers manually.

Sources: [1]

Before adoption

Source from Packer 1.10 onward is BUSL-1.1 rather than an OSI open-source license

Packer 1.10.0 and later are licensed under BUSL-1.1. The license permits specified production uses but restricts competitive hosted or embedded offerings against IBM's paid versions, and each version changes to MPL-2.0 after four years.

Sources: [4][1]

Version 1.16.1 uses Go 1.26.8 and includes plugin and security-related updates

The release updates the build toolchain to Go 1.26.8 and changes plugin retrieval, WinRM settings, gRPC dependencies, and other components. Review source-build and plugin compatibility during upgrades.

Sources: [2][3]

Official sources

  1. [1]Packer v1.16.1 README(2026-10-04)
  2. [2]Packer v1.16.1 release(2026-10-04)
  3. [3]Packer v1.16.1 Go version(2026-10-04)
  4. [4]Packer v1.16.1 BUSL-1.1 license(2026-10-04)
Supplemental curator note

Packer 1.10 and later are source-available under BUSL-1.1, not an OSI open-source license. Review license terms for competitive hosted or embedded offerings.

Try it in 3 steps

  1. 1

    Pull the Packer 1.16.1 container image with an exact pin

    Fetch the CLI environment pinned to 1.16.1 instead of using latest.

    docker pull hashicorp/packer:1.16.1
  2. 2

    Check the version without starting any image build

    Verify the Packer CLI version without cloud credentials or builder plugins.

    docker run --rm hashicorp/packer:1.16.1 version
  3. 3

    Inspect the plugin command surface

    Review external-plugin management without creating a machine image. Pin required_plugins before a real build.

    docker run --rm hashicorp/packer:1.16.1 plugins --help
Check the official README

Growth

Growth trends · Last 30 days

15,809 Stars

Trend data is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data
Stars
15,809
Forks
3,340
Watchers
15,809
Open issues
320
Owner type
Organization
Primary language
Go
License
BUSL-1.1
Repository last updated
Oct 4, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?