Brief summary of Docker's key components :

1. Docker Daemon :

   • The Docker daemon (also known as dockerd) is a background service that manages Docker containers on a host system.

   • It is responsible for building, running, and managing containers.

   • The Docker daemon listens for Docker API requests and communicates with the container runtime to execute those requests.

   • It typically runs as a system service and handles the low-level container operations.

2. Docker Client :

   • The Docker client (usually invoked using the docker command) is a command-line tool that allows users to interact with the Docker daemon.

   • Users issue commands to the Docker client to perform various tasks like creating containers, building images, managing volumes, and more.

   • The Docker client communicates with the Docker daemon via the Docker API to carry out these actions.

   • It acts as the primary interface for users to control and manage Docker containers and resources.

3. Docker Socket :

   • The Docker socket (typically /var/run/docker.sock on Unix-based systems) is a Unix socket that serves as a communication channel between the Docker client and the Docker daemon.

   • When a Docker client issues a command, it sends a request to the Docker socket.

   • The Docker daemon, in turn, listens to this socket and processes the client's request, executing the requested Docker operation.

   • This socket allows secure communication between the client and the daemon without exposing the Docker API over a network port.

In summary, the Docker daemon is responsible for managing containers, the Docker client is the user interface for interacting with Docker, and the Docker socket serves as the communication bridge between the client and the daemon, enabling users to control and manage containers and resources on a host system.