Book Image

Mastering Docker Enterprise

By : Mark Panthofer
Book Image

Mastering Docker Enterprise

By: Mark Panthofer

Overview of this book

While known mostly as the open source engine behind tens of millions of server nodes, Docker also offers commercially supported enterprise tooling known as the Docker Enterprise. This platform leverages the deep roots from Docker Engine - Community (formerly Docker CE) and Kubernetes, but adds support and tooling to efficiently operate a secure container platform at scale. With hundreds of enterprises on board, best practices and adoption patterns are emerging rapidly. These learning points can be used to inform adopters and help manage the enterprise transformation associated with enterprise container adoption. This book starts by explaining the case for Docker Enterprise, as well as its structure and reference architecture. From there, we progress through the PoC,pilot and production stages as a working model for adoption, evolving the platform’s design and configuration for each stage and using detailed application examples along the way to clarify and demonstrate important concepts.The book concludes with Docker’s impact on other emerging software technologies, such as Blockchain and Serverless computing. By the end of this book, you’ll have a better understanding of what it takes to get your enterprise up and running with Docker Enterprise and beyond.
Table of Contents (17 chapters)
Free Chapter
1
Section 1: Getting Started with Docker Enterprise
5
Section 2: Piloting Docker Enterprise
10
Section 3: In Production with Docker Enterprise

Chapter 4: Prepare the Docker Enterprise Pilot Cluster

  1. Here are the differences between the Docker0 default network and the custom bridge network:
    • The default network does not provide DNS
    • Customer networks provide DNS using the container's explicit name (using the --name parameter) 
  1. Yes, if you are running in Swarm mode. Create two Swarm services and connect them to the same overlay network.
  2. Here are two recommended ways for a cluster user (such as a developer, DevOps, or system administrator) to access the cluster:
    • UCP web UI
    • UCL client bundle
  1. The UCP Controller runs on the (Swarm) manager nodes. 
  1. Clock skew causes problems when validating a certificate-based connection. UCP uses certificates to secure the cluster communications and it does not take too much for the difference in clocks to drift outside of a certificate's validity...