Docker

Docker is an open-source platform used to package, distribute, and run applications within isolated environments called containers. It allows developers to bundle an application with all its necessary parts—such as libraries and dependencies—to ensure it runs consistently across different computing environments.

Before Docker

Before Docker, deploying applications across different environments was a nightmare. Differences in dependencies, library versions, and OS configurations led to the infamous “works on my machine” problem.

Core Components

Docker Engine: The core client-server application that builds and runs containers using Docker components and services.

Docker Image: A read-only template used to create containers; it contains the code, runtime, and libraries.

Docker Container: A live, runnable instance of an image that runs as an isolated process on the host machine.

Dockerfile: A text file containing instructions to automatically build a Docker image.

Docker Hub: A cloud-based registry for finding and sharing container images.

Docker’s Solution:

Docker solves this by standardizing the runtime environment. By bundling the application code with its specific dependencies into a single unit, it ensures the software runs identically whether it’s on a developer's laptop, a test server, or a cloud cluster.

• Portability: Runs anywhere in local machine, cloud, on‑prem servers.
• Consistency: Same behavior in development, testing, and production.
• Lightweight: No full OS per app; containers share the host kernel.
• Scalability: Ideal for microservices and orchestrators like Kubernetes and Docker Swarm.
• Efficiency: Starts in seconds, uses fewer system resources.
• Docker Architecture and Working

Docker makes use of a client-server architecture.

• The Docker client talks with the docker daemon which helps in building, running, and distributing the docker containers.
• The Docker client runs with the daemon on the same system or we can connect the Docker client with the Docker daemon remotely.
• With the help of REST API over a UNIX socket or a network, the docker client and daemon interact with each other.
• The Docker Client (CLI): The primary way users interact with Docker. When you type docker run, the client sends this command to the daemon via a REST API.
• The Docker Daemon (dockerd): The background service (server) that manages Docker objects such as images, containers, networks, and volumes.
• Docker Registry (Docker Hub): A storage system for Docker images. Docker Hub is the largest public registry, allowing developers to share and pull pre-configured images (like Ubuntu, MySQL, or Nginx).
• Docker Engine

Without the Docker Engine, Docker images cannot be built or containers executed.

• The Client sends Docker commands (docker build, docker run, etc.).
• The Daemon receives these commands and performs container operations.
• The REST API is the interface enabling this communication.
• In short, the Docker Engine is the runtime that makes containerization possible by connecting the Docker client with the daemon to build and manage containers efficiently.

Dockerfile

The Dockerfile uses DSL (Domain Specific Language) and contains instructions for generating a Docker image. Dockerfile will define the processes to quickly produce an image. While creating your application, you should create a Dockerfile in order since the Docker daemon runs all of the instructions from top to bottom.