One major issue when working with containers is their deprecation and maintenance costs. Too often, containers are built one day, shipped to production because they work, and forgotten there until the next rebuild (which may not happen anytime soon). Libraries are still libraries, and security fixes are pushed every day into distributions package repositories. Sysadmins are used to patch the systems; however, now it's a total anti-pattern to update a running container. Containers need to be rebuilt, exactly like developers are used to rebuilding applications with updated libraries to get rid of bugged code. The exception is that we are lucky enough to have tools that monitor each and every layer of our Docker images and tell us how and when they are vulnerable, allowing us to simply rebuild and redeploy them.
Infrastructure as Code (IAC) Cookbook
By :
Infrastructure as Code (IAC) Cookbook
By:
Overview of this book
Para 1: Infrastructure as code is transforming the way we solve infrastructural challenges. This book will show you how to make managing servers in the cloud faster, easier and more effective than ever before. With over 90 practical recipes for success, make the very most out of IAC.
Table of Contents (18 chapters)
Infrastructure as Code (IAC) Cookbook
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Free Chapter
Vagrant Development Environments
Provisioning IaaS with Terraform
Going Further with Terraform
Automating Complete Infrastructures with Terraform
Provisioning the Last Mile with Cloud-Init
Fundamentals of Managing Servers with Chef and Puppet
Testing and Writing Better Infrastructure Code with Chef and Puppet
Maintaining Systems Using Chef and Puppet
Working with Docker
Maintaining Docker Containers
Index
Customer Reviews