What is Docker ?
Docker is an open-source platform for building distributed software using “containerization."
Docker allows you to decouple the application/software from the underlying infrastructure into standardized units called containers that have everything the software needs to run including libraries, system tools, code, and runtime.
Why Docker ?
Docker containers are minimalistic and enable portability.
Docker lets applications and their environments be kept clean and minimal by isolating them, which allows for more granular control and greater portability.
Docker containers enable composability.
Containers make it easier for developers to compose the building blocks of an application into a modular unit with easily interchangeable parts, which can speed up development cycles, feature releases, and bug fixes.
Docker containers ease orchestration and scaling.
Because containers are lightweight, developers can launch lots of them for better scaling of services. These clusters of containers do then need to be orchestrated, which is where Kubernetes typically comes in.
What is Virtualization?
Virtualization is the process of creating virtual enviroment or virtual machine by spliting one system into many different sections which act like separate, distinct individual systems. A software called Hypervisor makes this kind of splitting possible.
What is Containerization ?
Containerization is a form of virtualization through which applications are run in containers (isolated user spaces) all using a shared OS. It packs or encapsulates software code and all its dependencies for it to run in a consistent and uniform manner on any infrastructure.
Virtual Machine vs Docker ?
Virtual Machines (VMs) virtualize the underlying hardware. They run on physical hardware via an intermediation layer known as a hypervisor. They require additional resources are required to scale-up VMs.
They are more suitable for monolithic applications. Whereas, Docker is operating system level virtualization. Docker containers userspace on top the of host kernel, making them lightweight and fast. Up-scaling is simpler, just need to create another container from an image.
What is Hypervisor?
A hypervisor is a software that makes virtualization possible. It is also called Virtual Machine Monitor. It divides the host system and allocates the resources to each divided virtual environment.
What are Docker Images?
A Docker image is an executable file, that creates a Docker container. An image is built from the executable version of an application together with its dependencies and configurations. Running instance of an image is a container.
Docker image includes system libraries, tools, and other files and dependencies for the application. An image is made up of multiple layers.
What is Docker Hub?
Docker images create docker containers. There has to be a registry where these docker images live. This registry is Docker Hub. Users can pick up images from Docker Hub and use them to create customized images and containers. Currently, the Docker Hub is the world’s largest public repository of image containers.
Components of Docker Architecture.
The four major components of Docker are daemon, Client, Host, and Registry
Docker daemon: It is also referred to as ‘dockerd’ and it accepts Docker API requests and manages Docker objects such as images, containers, networks, and volumes. It can also communicate with other daemons to manage Docker services.
Docker Client: It is the predominant way that enables Docker users to interact with Docker. It sends the docker commands to docker, which actually executes them using Docker API. The Docker client can communicate with more than one daemon.
Docker Registry: It hosts the Docker images and is used to pull and push the docker images from the configured registry. Docker Hub is the public registry that anyone can use, and Docker is configured to look for images on Docker Hub by default. However, it is always recommended for organizations to use own private registry.
Docker Host: It is the physical host (VM) on which Docker Daemon is running and docker images and containers are created.
What is Docker Engine?
Docker daemon or Docker engine represents the server. The docker daemon and the clients should be run on the same or remote host, which can communicate through command-line client binary and full RESTful API.
What is Docker Image Registry?
A Docker image registry, in simple terms, is an area where the docker images are stored. Instead of converting the applications to containers each and every time, a developer can directly use the images stored in the registry.
This image registry can either be public or private and Docker hub is the most popular and famous public registry available.
What are Dockerfiles?
Dockerfile is a text file that has instructions to build a Docker image. All commands in dockerfile could also be used from the command line to build images.
Sample Dockerfile :
FROM ubuntu:16.04
COPY . /app
RUN make /app
CMD python /app/app.py
Each instruction in a dockerfile creates one read-only layer:
Docker Network
Bridge
The Bridge network assigns IPs in the range of 172.17.x.x to the containers within it. To access these containers from outside you need to map the ports of these containers to the ports on the host.
Host
The Host network will remove any network isolation between the docker host and the containers. For instance, if you run a container on port 5000, it will be accessible on the same port on the docker host without any explicit port mapping. The only downside of this approach is that you can not use the same port twice for any container.
None
The None network keeps the container in complete isolation, i.e. they are not connected to any network or container.
To create Network:
docker network create --driver driver_name network_name
Types of Volume mounts in Docker.
There are three mount types available in Docker
Volume mounts are the best way to persist data in Docker. Data are stored in a part of the host filesystem which is managed by Docker containers. (/var/lib/docker/volumes/ on Linux)
-v or --volume flag and --mount flag could be used for docker swarm services and standalone containers.
To create a docker volume. For eg:
docker volume create my-vol
Inspect a volume
docker volume inspect my-vol
If we need to start a container with “my-vol”
With -v flag
docker run -d --name devtest -v my-vol:/app nginx:latest
Here nginx images with the latest tag are executed with using volume mount “my-vol”
With --mount flag
docker run -d --name devtest --mount \ source=my-vol,target=/app nginx:latest
Bind mounts may be stored anywhere on the host system. A file or directory on the host machine is mounted into a container unlike volume mounts where a new directory is created within Docker’s storage directory on the host machine, and Docker manages that directory’s contents. Non-Docker processes on the Docker host or a Docker container can modify them at any time.
tmpfs mounts are stored in the host system’s memory only and are never written to the host system’s file system. When the container stops, the tmpfs mount is removed, and files won’t persist.
Top comments (0)