ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop duplicating Packer templates per environment. Typed HCL2 variables, templatefile() for external scripts, and post‑processors turn one template into a small image factory.
Keep Packer image builds DRY by using HCL2 variable blocks and external .pkrvars.hcl files. One template, multiple environments, and validation before every build.
Stop duplicating installation scripts across cloud regions. Learn how to use Packer's source and build blocks to decouple infrastructure from configuration.
Use Packer 1.6+ HCL2 to parameterize builders, provisioners, and post‑processors. This guide shows the minimal design, trust boundaries, and operational checks for a reusable, version‑controlled image build workflow.
If you need to produce VM or cloud images for both amd64 and arm64, Packer’s new multi‑arch syntax lets you do it in one run. This post shows the exact HCL2 syntax, a working example, and what to watch out for.
Learn how Packer's HCL2 Multi‑Build feature lets you define one set of provisioners and create identical AWS AMIs and Azure Images in a single run, eliminating image drift.
DNS Resolution Timing in Packer HCL2 Templates When configuring Packer templates with multiple network interfaces or custom DNS settings, there is an unresolved question about when DNS resolution occurs relative to template validation and builder initialization. The HCL2 syntax allows defining custom DNS servers through builder configurations like dns_server
Artifact Upload Reliability When utilizing HCL2-based builds, Packer employs post-processors to transition build outputs—such as snapshots—into registered cloud artifacts. This integration boundary relies on the underlying provider SDKs to manage network-level failures and API retries. Consistency Constraints Because Packer lacks a global retry configuration
When utilizing the Amazon EBS builder in HashiCorp Packer (HCL2), the lifecycle of the temporary instance is managed via specific shutdown configurations. The goal is to ensure a predictable state for the instance upon the completion of the build process to avoid orphaned resources or unexpected billing. There is an ambiguity regarding how Packer interacts w