ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #packer
Packer hangs on "Waiting for SSH/WinRM" until the timeout kills the instance and the evidence. A cause table, ordered checks, targeted fixes, and escalation criteria.
Learn how to use Packer's HCL2 variables and locals to share common settings across multiple builders, keep templates DRY, and switch between environments with a single file.
When Packer stalls at the communicator stage, the build log freezes at "Waiting for SSH to become available…". This guide maps symptoms to causes, walks through ordered checks, and links fixes to findings so you can pinpoint network, authentication, or timing problems in cloud builders.
Diagnose and fix common Packer amazon‑ebs build problems—incremental snapshots, IAM permissions, and unique AMI naming—step‑by‑step with real commands and verifications.
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.
Using Packer’s shell‑local post‑processor lets you run host‑only scripts after an AMI build, keeping the image clean and adding side‑effects like Docker image creation or artifact upload. This article walks through a concrete example, trade‑offs, and actionable steps.
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.
ssh
aws