Book Image

HashiCorp Packer in Production

By : John Boero
Book Image

HashiCorp Packer in Production

By: John Boero

Overview of this book

Creating machine images can be time-consuming and error-prone when done manually. HashiCorp Packer enables you to automate this process by defining the configuration in a simple, declarative syntax. This configuration is then used to create machine images for multiple environments and cloud providers. The book begins by showing you how to create your first manifest while helping you understand the available components. You’ll then configure the most common built-in builder options for Packer and use runtime provisioners to reconfigure a source image for desired tasks. You’ll also learn how to control logging for troubleshooting errors in complex builds and explore monitoring options for multiple logs at once. As you advance, you’ll build on your initial manifest for a local application that’ll easily migrate to another builder or cloud. The chapters also help you get to grips with basic container image options in different formats while scaling large builds in production. Finally, you’ll develop a life cycle and retention policy for images, automate packer builds, and protect your production environment from nefarious plugins. By the end of this book, you’ll be equipped to smoothen collaboration and reduce the risk of errors by creating machine images consistently and automatically based on your defined configuration.
Table of Contents (18 chapters)
1
Part 1: Packer’s Beginnings
7
Part 2: Managing Large Environments
11
Part 3: Advanced Customized Packer

Adding a Google GCP build

Google Compute is actually the simplest of the three large cloud plugins. It offers just a single unified builder that boots a VM for each build. The advantage is simplicity. The disadvantage is that there is not currently a chroot builder option in GCP to accelerate builds. Also, the Google Compute plugin makes heavy usage of the gcloud CLI, which must be installed on the Packer host for some use cases. Note that Google has fairly strict regular expressions on resource names, so underscores and dots are not allowed in most cases. However, GCP is happy to provide the expected regular expression when a naming issue occurs:

'(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?)'

When adding GCP, there is a fresh set of environment variables that are handy to import as variables. These can be defaulted whether or not they are actually present as environment variables. An unset environment variable will result in a valid NULL variable in Packer, which may or may...