Docker Architecture Components and Networking

• The Docker architecture uses a client-server model that includes the Docker Client, Docker Host, Network and Storage components.
• The Docker Client is used to pull images and run containers.
• The Docker Host is where all the components of the Docker architecture are configured to run.
• Docker networking is used to establish communication between Docker containers and the outside world.
• Docker supports different types of networks, each fit for certain use cases.
• Docker handles communication between containers by creating a default bridge network, so you often don’t have to deal with networking and can instead focus on creating and running containers.
• The host network is a docker architecture’s network driver that allows containers to use the network provided by the host machine.
• None is a docker architecture’s network driver that lets you isolate containers from each other and the external network.
• Overlay is a docker architecture’s network driver that is for multi-host network communication.
• Macvlan is a docker architecture’s network driver that lets us connect Docker containers directly to the physical host network.
• Docker provides a variety of mechanisms for persisting data, including data volumes and directory mounts.
• Storage plugins enable Engine deployments to be integrated with external storage systems, such as Amazon EBS.
• Docker registries are a way to share custom docker images with everyone.
• Public registries are a way to share custom docker images with everyone.

Explore the components of the Docker architecture, including the Docker Client, Docker Host, networking options, and mechanisms for persisting data. Learn about different network drivers and storage plugins, as well as the use of Docker registries to share custom images.