Skip to main content
Hello and welcome! In this lesson, we’ll explore the components and architecture of Docker Enterprise Edition (Docker EE). Docker Engine is available in two major editions:
  • Docker CE (Community Edition): the free, open-source version
  • Docker EE (Enterprise Edition): the certified, enterprise-grade version
Since November 2019, Mirantis Inc. maintains Docker EE. Built for developers and IT teams, Docker EE enables you to build, share, and run business-critical applications at scale with enterprise-grade security and management. Docker EE comprises three core components:
  • Docker Engine Enterprise: Certified container runtime with FIPS compliance
  • Universal Control Plane (UCP): Web-based cluster management portal with role-based access control (RBAC) and LDAP/AD integration
  • Docker Trusted Registry (DTR): Private, secure image storage behind your firewall
UCP supports both Docker Swarm and Kubernetes on the same cluster. You can label nodes as Swarm workers, Kubernetes workers, or both, then deploy services across them.
The image shows a presentation slide about Docker Enterprise Edition by Mirantis, featuring a dashboard interface with options like Access Control and Kubernetes.
Docker Trusted Registry integrates seamlessly with UCP and Engine. You can deploy Docker EE clusters on-premises, in public clouds, or in hybrid environments.
The image is a presentation slide about Docker Enterprise Edition by Mirantis, highlighting features like security, access control, and Kubernetes service. It also shows a user interface for Docker Enterprise Trusted Registry.

​
High-Level Setup

Follow these steps to get Docker Enterprise up and running:
  1. Provision your infrastructure (manager and worker nodes)
  2. Install Docker Engine Enterprise on all nodes
  3. Deploy Universal Control Plane (UCP) on manager nodes
  4. Install Docker Trusted Registry (DTR) on designated worker nodes

​
Infrastructure Prerequisites

Ensure your environment meets the following requirements before installing UCP or DTR:
  • Linux kernel version ≥ 3.10
  • Static IP address configured for each node
  • Bi-directional network connectivity between nodes
  • NTP configured for accurate time synchronization
  • User namespaces disabled (not currently supported)
  • Docker Engine Enterprise installed on every node
User namespaces must be disabled or UCP deployment will fail.
The image lists pre-requisites for a system setup, including Linux Kernel version, static IP, network connectivity, time sync, user namespaces, and Docker Engine requirements.

​
UCP & DTR Configuration Requirements

Docker UCP and DTR each have minimum and recommended hardware specifications. Use minimum specs for testing or proofs of concept; follow recommended specs for production environments.

​
UCP Requirements

SpecificationMinimum (Test)Recommended (Production)
RAM (manager)8 GB16 GB
vCPUs (manager)2 vCPUs4 vCPUs
Disk on /var (manager)10 GB25–100 GB
RAM (worker)4 GB4 GB
Disk on /var (worker)500 MB500 MB
The image lists the minimum requirements for UCP, including RAM, vCPUs, and disk space for manager and worker nodes.

​
DTR Requirements

SpecificationMinimum (Test)Recommended (Production)
RAM16 GB16 GB
vCPUs2 vCPUs4 vCPUs
Free Disk10 GB100 GB
Network Ports80, 443 open80, 443 open
DTR must be installed on worker nodes within your UCP cluster.
The image lists the minimum requirements for DTR, including 16 GB of RAM, 2 vCPUs (with a note for 4 vCPUs), 10 GB of free disk space (noting 100 GB), and ports 80 and 443.

​
Sample Lab Topology

In this course lab, we’ll deploy:
  • 1 UCP manager node
  • 1 UCP worker node (for DTR)
  • 1 DTR instance
  • 3 UCP managers (high-availability quorum)
  • 3 UCP workers (DTR hosts)
  • 3 DTR replicas
  • 3 load balancers (one each for managers, workers, and DTR)

Watch Video