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

Grand conclusion

As we come to a close, I hope you’ve learned some helpful tricks to add to your Packer templates. Even though Packer is one HashiCorp’s simplest tools and projects, it’s incredible what you can do with it. Often, people think of Packer as just a tool for building cloud images. Packer is that and much more, with the ability to build and test everything from mobile applications on ARM devices to embedded microcontroller applications and containers. All of this can be done within a single template or template directory. Remember, a lot of old Packer code is written in a legacy JSON format that is still supported for backward compatibility, but new templates should be written in HCL2 or the new pkr.json format.

Don’t forget the cost savings from making sure your application is built and tested for alternative architectures such as ARM or AArch64 and AWS Graviton. This step alone can save you 50% or more on your compute spend. Also, being...