Docker-engine Architecture has four elements – Client, Daemon, Private registry, and Hub. Its prime purpose is to port Software applications from one location to another (For instance, local server to cloud).
The principle Docker followed is, hard-labor shifts goods of different sizes from one place to another piece by piece. This process time-consuming and laborious. Based on the same example, Docker Architecture was designed to simplify the process.
Here process means porting of applications from one location to another.
Docker supports Containers, which you can use to port your code to various regions – Unit, Integration, and Live (Production) in a lesser time. These contain images (applications and their libraries), and these are executable. You may also like Vmware ovftool vmx to ova Convert Errors Resolved.
Four Components of Docker Architecture.
Table of Contents
Architectural diagram of Docker.
Docker supports HTTP protocol. When you install Docker on your machine, your interaction will be with the client – to send or receive instructions.
It is a server, which receives instructions from the Docker client. You cannot directly interact with it. In the diagram, it has shown with a two-way arrow (so the server receives and sends responses to the client). The communication will be with the HTTP protocol.
Registries store images that contain libraries to run an application. You can call these snap-shots ( read-only code). With the images, you can create a container that is executable. Check out what is Docker image?.
Hub is a public registry, which is maintained by Docker Inc. You can find a lot of preinstalled images, which a user can pull and do the experiment, and modify. The communication between Docker Hub and Daemon will be through the HTTP protocol.