Loading content
Docker allows developers to package applications in containers that include all necessary dependencies. This simplifies the deployment and scaling of applications across different environments.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Docker is a platform for building, packaging, distributing, and running applications in isolated containers.
Docker was released in 2013 and made Linux containers broadly accessible to development teams through images, Dockerfiles, registries, and an approachable CLI.
A Dockerfile describes reproducible image layers. The engine creates an immutable image and starts containers as isolated processes using namespaces and cgroups; volumes persist data, while networks connect services. Registries distribute images through tags and digests.
A versioned filesystem and metadata form the deliverable artifact.
An isolated process instance runs the image with runtime configuration.
Central storage distributes images between build and operating environments.
Docker creates consistent development and delivery artifacts and simplifies local dependencies. Images need patching, least privilege, secret separation, provenance, and scanning; containers are not a complete security boundary.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.