Understanding the Docker Terminology

Containerization of applications was made popular by Docker (https://www.docker.com/). Its popularity is so much that it has become a synonym for containers. Let’s understand the Docker terminology.

Docker Image

Docker images are blueprints of our application which form the basis of containers. 

Docker Registry

 Docker registry contains various images in such a manner that, if a set of information on images can be retrieved or used, it’s called a library of images. 

Docker Hub

This is a public registry that stores images. 

Docker File

Docker File is a build or scripting file that contains instructions that we can use to build a Docker image. Multiple steps can be documented in a Docker File, starting with getting the base image.

Docker Container

An instance of a Docker image is called a Docker container.

Docker Compose

Docker compose allows you to define an application’s components—their containers, configuration, links, and volumes—in a single file.

Docker Swarm

Swarm is the Docker service where container nodes work together. It runs a defined number of instances of a replica task, which is itself a Docker image.

Docker Daemon

The background service running on the host that manages building, running and distributing Docker containers. The daemon is the process that runs in the operating system which clients talk to.

Docker Client 

The command-line tool that allows the user to interact with the daemon. More generally, there can be other forms of clients too – such as Kitematic which provide a GUI to the users.

You might be interested in the following courses:

Course Category

Back to: Microservices with C#, .NET Core and Azure > Deployment