Packer

Packer is a tool that builds identical machine images for multiple platforms from a single source configuration.

  • Infrastructure
  • Tools & Utilities
Packer is a tool that builds identical machine images for multiple platforms from a single source configuration. It runs on every major operating system and creates images in parallel, with many build targets available through plugin integrations. Use it to generate VMs, Vagrant boxes, and cloud images consistently across your infrastructure.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

76/100 Good

Maintained
100last commit 1 day ago
Popular
8415,825 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM
Security check
84no serious findings, CI, tests, OpenSSF Scorecard 6/10
GitHub stars
15,825
Open issues
315
Last commit
2026-11-20
Latest release
v1.16.2
Activity
steady

Checked yesterday - source: GitHub (hashicorp/packer)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 1 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install plugins before you build Add a required_plugins section that lists the add-ons your Packer recipe needs, then run packer init. This makes Packer download those add-ons, and without it Packer stops with a missing plugin error. source
  • Reference your source in the build Define a source block (a named description of what to build) and list its full label, like source.scaffolding.example, in build.sources. If the label is missing or misspelled, Packer does not know which target to build and stops. source
  • Save the finished build with mock If you use the scaffolding post-processor (the final step that saves the image), set mock to the output file path, such as builds/scaffolding.box. Without this required value, Packer has nowhere to write the finished build. source

Fetched 48 days ago - each note links to its source

Alternatives (4)

  • Davit - Fully native macOS interface for running Linux containers on Apple silicon, with direct daemon communication, one-click terminals, live sta…
  • Docker - Docker (Moby) is the open-source engine that builds and runs containerized applications, forming the foundation of the Docker ecosystem for…
  • Docker Desktop - Docker Desktop is a one-click-install application that lets you to build, share, and run containerized applications and microservices.
  • Vagrant - Create and manage virtualized development environments.

Checked 54 days ago - source: AlternativeTo

Common questions

How do I make Packer download the required builder or provisioner plugins for a template?

Add a required_plugins section that lists the add-ons your Packer recipe needs, then run packer init. Without this, Packer stops with a missing plugin error.

Why does Packer stop when it cannot find the build target?

Define a source block and reference its full label, such as source.scaffolding.example, in build.sources. If the label is missing or misspelled, Packer does not know which target to build and stops.

What must I set so the scaffolding post-processor can save the finished build?

Set mock to the output file path, such as builds/scaffolding.box. Without this required value, Packer has nowhere to write the finished build.

What common problems should I check when building Proxmox templates with Packer?

Look for authentication failures, SSH connection timeouts, ISO download errors, boot command issues, and distribution-specific configuration problems.

Answers sourced from deepwiki.com, github.com, github.com, github.com

Community

Collected 48 days ago - public community threads