Docker uses a client-server architecture. It communicates with Docker daemon, which lifts, Run and Distributes your Docker containers. Docker client and daemon run on the same system. Both exchange information by REST API. Over UNIX sockets.
1.Docker Architecture Sections:
Know more about Docker Architecture by Docker Online Training.a)Daemon:
It works for Docker API Requests. Manage Docker Objects like. Volumes, Containers, Networks. Specifically, It Interacts with some other Daemons. Accordingly for managing Docker Services. Similarly, Every swarm is a Docker Daemon. It will communicate in the background.
b)Client:
Generally, the client is the best way to interact with Docker. When you use certain Commands like Docker run. It Sends these commands to Docker. Besides Docker command it uses. Docker API, it communicates with one or many Daemons.
c)Registries:
Especially a Docker registry stores Docker images. Docker Hub is an open public Registry, anyone can use it. As in Default Docker is Configured to look into Images.
You have an option to Run. Your Own Private Registry. If you use Docker Data Center. On the other hand. It includes Docker Trusted Registry.
If you use Docker Pull or Docker Run commands. The Required Images were Pulled from your Configured Registry. Or If you use Docker Push command. Your Image is Pushed to your Configured Registry.
2.Docker Objects:
Especially When you use Docker. You make and use Images, holders, systems, volumes, modules, and other objects. It is a short outline. For some of those objects.
a)Images:
Generally, the image is a read-only template with instructions for making a Docker container. Often, an Image depends on another Image. With some extra customization.
For instance, you may fabricate an Image which depends on the Image. However, introduces the Apache web server and your application. Additional configuration is required to influence your application to run.
You can Design Images or, You can use only those designed by your Friends. In addition, that was published in a Registry. To build your Own Image, you Design in a Docker file.
With a simple Syntax. For Defining Steps you need, to design Image and Run. Every Instruction.
b)Containers:
A Container is Defined as a Run able, Example of an Image. You can Move, Delete, Stop, Start a container. By using Docker CLI or API. We Can connect a Container, with many other Networks. An instance of command is the Docker run command.
Above command Runs on Ubuntu container. Subsequently, it connects interactively. To your local command-line session. It operates /bin/bash.
c)Services:
Generally With Services. Everyone scale containers on many Docker Daemons. Which works Together like a Swarm. With multiple Workers and Managers. Every member of a Swarm is a Docker Daemon. All Daemons will communicate.
3.Underlying Technology:
Docker was made by GO. Which take Profit of Features. like the Linux Kernel.
a)Name Spaces:
Docker uses Technology. known as Name Space. For Offering Single Work-space. Known as a Container. With this in mind. When you run a container. It Designs a Set of Namespace. For Container in short.
b)Control Groups:
Docker Engine runs on Linux Relies. Another technology, known as Control Groups. In the same way. A Group limits an Application. While it may be true. In the Future, Docker uses formats. like BSD, Jails and Solaris Zones.
4.Union File Systems:
Docker uses Union FS, For Building Blocks and containers. With this purpose in mind. It, use Multiple union Variants. It contains AU FS, bt RFS. Surely a Device Mapper.
a)Container Format:
Docker Engine Combines namespaces, control groups. And Union FS into a wrapper. It is known as Container Format. The default container is a lib container.
I think you have got an overview of Docker Architecture. These are the best, Known Facts about Docker Architecture, in upcoming blogs, we will update more data on this Topic.