I'm learning Docker and have been building a mental model of how it works: an image packages software and its dependencies into files, and the Docker daemon uses that image to create an isolated process called a container. That abstraction makes sense to me, but Docker describes a container as a "standard unit of software." What exactly does "standard" mean in this context?
3 Answers
Before containers became common, developers often delivered source code or compiled binaries while operations teams separately configured the server, language runtime, libraries, and other dependencies. Differences between environments could then cause failures in production. A container image standardizes the deployment unit by bundling the application with its user-space runtime environment. Any compatible container platform can run that image, which makes the division between application setup and infrastructure clearer, even though the responsibilities can still overlap in practice.
The phrase is an analogy to standardized shipping containers. Ships, trucks, and ports can handle the same container format without needing to know what is inside. Similarly, container tools can run an image using the same general process whether it contains a single compiled program, a full application stack, or software written in Go, Rust, Java, or PHP. The runtime mostly treats it as a uniform package.
Here, “standard” mainly means packaged in a predictable, portable form. A container image includes the application and the user-space files it needs, so the infrastructure running it does not have to understand the application’s language or dependencies. The host still provides the kernel, and isolation uses operating-system features such as namespaces and cgroups. It’s similar in spirit to installing a package, but the container provides a more consistent runtime boundary.
Exactly—the server sees the same kind of runnable package whether it contains a Python script or a large Java application. The contents vary, but the way the infrastructure starts and manages it stays consistent.
That clears it up—so the standard is mainly the consistent packaging and execution interface, not that every container contains the same kind of software.