oowy/packer repository overview

⁠Quick reference

• Maintained by:
  Oowy team⁠

• Where to get help:
  the Docker Community Slack⁠, Server Fault⁠, Unix & Linux⁠, or Stack Overflow⁠

⁠Supported tags

Based on Alpine Linux 3.20

• latest
• 1.12.0-alpine3.20

Based on Alpine Linux 3.19

• 1.11.2-alpine3.19
• 1.11.1-alpine3.19
• 1.11.0-alpine3.19
• 1.10.3-alpine3.19
• 1.10.2-alpine3.19
• 1.10.1-alpine3.19
• 1.10.0-alpine3.19
• 1.9.5-alpine3.19

Based on Alpine Linux 3.18

• 1.10.3-alpine3.18
• 1.10.2-alpine3.18
• 1.10.1-alpine3.18
• 1.10.0-alpine3.18
• 1.9.5-alpine3.18
• 1.8.7-alpine3.18
• 1.7.10-alpine3.18
• 1.6.6-alpine3.18
• 1.5.6-alpine3.18
• 1.4.5-alpine3.18

Based on Alpine Linux 3.17

• 1.10.0-alpine3.17
• 1.9.5-alpine3.17
• 1.8.7-alpine3.17
• 1.7.10-alpine3.17
• 1.6.6-alpine3.17
• 1.5.6-alpine3.17
• 1.4.5-alpine3.17

⁠Quick reference (cont.)

• Supported architectures: amd64, arm64v8

⁠What is Packer?

Packer⁠ is a tool for creating identical machine images for multiple platforms (such as AWS, Azure, VMware, and Docker) from a single source configuration. It automates the process of image creation and makes it easy to create consistent and reproducible images across different platforms.

Running Packer inside a Docker container requires more configuration than running the Packer CLI executables directly. Unless you need container isolation, we recommend using [the non-containerized Packer CLI packages](the non-containerized Packer CLI packages).

⁠Packer Docker Images

The team publishes a Docker image to this repository for each official release of Packer CLI. Each versioned image includes the Packer CLI release with the same version number.

These images wrap the Packer executable, allowing you to run Packer subcommands by passing in their names and arguments as part of docker run.

For example, the command below uses the 'latest' tag to generate a 'build' using the most recent version of Packer:

  docker run -i -t oowy/packer:latest build .

Note that for production use, we recommend specifying a specific version instead of using latest.

⁠Configuration

You will likely need to further configure your container so that Packer can access your configuration files and provider credentials. This could include mounting your configuration into the container, setting the working directory to refer to your configuration, and passing in environment variables and credentials files for the providers you intend to use. The docker run documentation lists the options you can use to customize the container environment.

You could also use these images as a base for your own images. For example, this would be helpful if you wanted to to pre-set CLI Configuration settings as part of your image.

⁠Community

Open issues about Packer binary on the main Packer repository⁠.