Menu

1 / 4

Docker Architecture: The Client, the Daemon, and the Engine

DEV Community: docker·Amar·about 13 hours ago
#aq7Hlxwn
#devtodocker#devto#dev#container#docker
Reading 0:00
15s threshold

TL;DR: Docker architecture is a split between three programs: the docker CLI you type into, the dockerd daemon that obeys over a REST API, and a registry that supplies the layered, read-only images containers are made from.

Client and daemon are separate programs meeting over a REST API, a UNIX socket or a network link; one client can point at several daemons.

An image stacks read-only layers a union filesystem, OverlayFS most often, presents as one; a rebuild redoes only layers whose instructions changed.

A container is an isolated process on the host’s kernel: namespaces fence its view, cgroups cap memory and CPU.

The default bridge network keeps a container’s ports visible to the host yet invisible beyond it, until -p publishes one.

Delete a container and its writable layer dies with it; volumes carry on. containerd and runc create the container inside the Engine.

Every docker run you have ever typed drove three cooperating programs, and two of them never touched your screen.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.