A field manual for everything that ships in a container.

Docker, Kubernetes, and clusters in the cloud — explained with runnable examples instead of walls of spec. Build a Dockerfile by hand, look up any term, or copy a working compose stack.

Open the playground Browse the glossary

sh — docktionary

docker build -t docktionary/app:1.0 .

[+] Building 4.2s (9/9) FINISHED

=> [1/4] FROM node:22-alpine

=> [2/4] COPY package.json .

=> [3/4] RUN npm ci --omit=dev

=> [4/4] COPY . .

=> exporting to image

=> naming to docktionary/app:1.0

docker run -d -p 8080:80 docktionary/app:1.0

a3f9e1c6b2d4

docker ps

CONTAINER ID IMAGE STATUS PORTS

a3f9e1c6b2d4 docktionary/app:1.0 Up 2 seconds 0.0.0.0:8080->80/tcp

▏

DOCU 100001 4

Docker

Images, containers, volumes, networks, compose

KUBU 200002 1

Kubernetes

Pods, deployments, services, the control plane

CLDU 300003 8

Clusters & cloud

Managed clusters, autoscaling, storage, cost

GLSU 400004 5

Glossary

The docktionary itself — every term, defined

PLYU 500005 2

Playground

Build it by hand, or lint one you already have

SNPU 600006 9

Snippets

Ready-made Dockerfiles, compose stacks, manifests

INSU 700007 6

Inspector

Inspect a local image, look one up, or compare two

Term of the day · Kubernetes

Because Pods are mortal and get new IPs when recreated, a Service provides a stable address in front of a label-selected set of Pods, load-balancing across them. ClusterIP (internal), NodePort, and LoadBalancer are the main types, depending on how the traffic needs to arrive.

See every term