This blog will consist of basic terminologies from the architecture of docker and the eco-system of docker.
Docker Artectiture :
The user will create a Docker File which will include the task and requirements for the image.
Once the Docker file is created, it will be provided to the Docker engine to execute it and create a Docker image
The Docker engine will create a container by using the Docker image
Docker images can be shared with multiple users by pushing the image to the central repository i.e Docker Hub
Once the image is available on the docker hub, users who have access to that repository can able to access the image and create their container like user 1.
Docker Eco-System :
Docker Client :
It's a primary way to interact with the docker server/daemon.
Docker File is created.
It interacts with the docker engine using CLI and API.Docker Server
It runs on Host OS i.e where the docker engine is installed
It is responsible for creating the docker images with the Docker File.
Containers are created with the same docker images.
It also communicates with other daemons for other tasks.Docker Hub
It stores the images in a private or public repository.
Users can download the images stored in the docker hub and use them for creating the container.Docker Image
It's a read-only binary template.
Dependency and Requirements are mentioned in it.Docker Compose:
It is used for running multiple containers.
Way to create the image :
Take an image from the docker hub.
Create an image from the docker file.
Create an image from the existing container.