📦Containers
Packaging apps into portable containers · 25 terms
Container Basics
4What a container is, the kind set up for writing code, and the Linux features that wall it off and cap what it uses.
A sealed box that holds an app and all it needs. It runs the same anywhere.
A container set up as a place to code. Every coder gets the same tools.
A Linux trick that gives programs a private view of the system. Each box is built on it.
A Linux limit on memory and CPU. Each box gets its own cap.
Container Storage and Networking
4Where a container keeps files that must outlast it, and how it is reached from the host and from other containers.
Storage that outlives the container. Files kept there stay when the box is gone.
A host folder shared straight into a container. Edits on either side show on both.
A link from a host port to a port inside a box. It lets outside traffic in.
A private network that lets boxes talk to each other by name.
Images and Registries
5The package a container starts from, the label that names its version, the servers that store it and the open standard they share.
The saved pack that a container starts from. One image can start many of them.
The label after the colon in an image name. It often names a version.
A server that stores container images. You push them up and pull them down.
Docker's public store of images. The docker tool looks there first.
The group that writes the shared rules all image tools follow.
Image Builds
5The recipe file that builds an image, the image it starts from, the layers it adds and the files it leaves out.
A text file of steps. It builds a container image, one line at a time.
The first image a build starts from. It is named on the FROM line.
One saved set of file changes. Layers stack up to make a container image.
A build in steps. Only the finished app goes into the last image.
A file that lists what to leave out when an image is built.
Runtimes and Tools
7The programs that start containers, and the command-line tools people type into to run them.
The program under the hood that starts and stops containers. Other tools hand it the work.
The best-known tool to build and run containers. It all works from one command line.
The command that makes a new box from an image and starts it.
Runs one more command in a live box. Often it is a shell.
A rule for whether a stopped box should start up again.
A free tool that runs containers like Docker. No background service is needed.
A tool that starts a group of containers. One file and one command do it.