Return to site

DEVOPS: Docker architecture

ยท devops

The Docker architecture is designed by layered structure, which is described below:

โ€•Docker_Client

โ€•Docker_daemon / Docker_Host

โ€•Docker_registry

๐“๐ก๐ž ๐ƒ๐จ๐œ๐ค๐ž๐ซ ๐œ๐ฅ๐ข๐ž๐ง๐ญ

The Docker client (docker) is the primary way that many Docker users interact with Docker. When you use commands such as ๐’…๐’๐’„๐’Œ๐’†๐’“ ๐’“๐’–๐’, the client sends these commands to dockerd, which carries them out. The docker command uses the Docker API. The Docker client can communicate with more than one daemon.

๐“๐ก๐ž ๐ƒ๐จ๐œ๐ค๐ž๐ซ ๐๐š๐ž๐ฆ๐จ๐ง / ๐ƒ๐จ๐œ๐ค๐ž๐ซ ๐ก๐จ๐ฌ๐ญ

The Docker daemon (dockerd) listens for Docker API requests and manages Docker objects such as images, containers, networks, and volumes. A daemon can also communicate with other daemons to manage Docker services.

๐ƒ๐จ๐œ๐ค๐ž๐ซ ๐ซ๐ž๐ ๐ข๐ฌ๐ญ๐ซ๐ข๐ž๐ฌ

A Docker registry stores Docker images. Docker Hub is a public registry that anyone can use, and Docker is configured to look for images on Docker Hub by default. You can even run your own private registry.

When you use the ๐’…๐’๐’„๐’Œ๐’†๐’“ ๐’‘๐’–๐’๐’ or ๐’…๐’๐’„๐’Œ๐’†๐’“ ๐’“๐’–๐’ commands, the required images are pulled from your configured registry. When you use the ๐’…๐’๐’„๐’Œ๐’†๐’“ ๐’‘๐’–๐’”๐’‰ command, your image is pushed to your configured registry.

All Posts
ร—

Almost doneโ€ฆ

We just sent you an email.ย Please click the link in the email to confirm your subscription!

OK