Book Image

Windows Server 2019 Cookbook - Second Edition

By : Mark Henderson, Jordan Krause
Book Image

Windows Server 2019 Cookbook - Second Edition

By: Mark Henderson, Jordan Krause

Overview of this book

Do you want to get up and running with essential administrative tasks in Windows Server 2019? This second edition of the Windows Server 2019 Cookbook is packed with practical recipes that will help you do just that. The book starts by taking you through the basics that you need to know to get a Windows Server operating system working, before teaching you how to navigate through daily tasks using the upgraded graphical user interface (GUI). You'll then learn how to compose an optimal Group Policy and perform task automation with PowerShell scripting. As you advance, you’ll get to grips with faster app innovation, improved Windows security measures, and hybrid cloud environments. After you’ve explored the functions available to provide remote network access to your users, you’ll cover the new Hyper-V enhancements. Finally, this Windows Server book will guide you through practical recipes relating to Azure integration and important tips for how to manage a Windows Server environment seamlessly. By the end of this book, you’ll be well-versed with Windows Server 2019 essentials and have the skills you need to configure Windows services and implement best practices for securing a Windows Server environment.
Table of Contents (18 chapters)

Productionizing a running container

So far in this chapter, we've learned how to get containers up and running, and even how to build or customize container images. But in the previous recipe, I noted that you wouldn't actually want to run MongoDB in production in the way that I described. You may be wondering, why is that?

There are a few reasons. Firstly, containers are, by design, ephemeral – this means every time you restart a container, it's back to the state it was originally in. This is probably fine for something like a web server – but it's not fine for a database server. Imagine losing all your data every time you restarted your server! Secondly, we're not passing any configuration through to our containers. A lot of containers are designed to run with just ephemeral storage. This is not persistent, so how do we configure the software inside the container? There are other things we have to figure out if we're going to keep our...