Container
A packaged application process with its dependencies and isolated runtime configuration, sharing the host operating-system kernel.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/container/
01What it means
A software container packages an application and its runtime dependencies into an image that a container runtime starts as an isolated process. Operating-system mechanisms separate files, processes, networking, and resource use while containers share the host kernel. An image is the packaged template; a container is a running or stopped instance of it.[1][2]
- 01Image definitionFilesystem, runtime, dependencies, entry point
- 02Immutable imageDigest or controlled version
- 03RegistryProvenance, scanning, access control
- 04Container runtimeConfiguration, secrets, network, resource limits
- 05Replace + observeDeploy new instances; retain data externally
Containers isolate processes while sharing the host kernel; persistent data and secrets belong outside the disposable container filesystem.
02Why it matters
Containers make application environments more repeatable across development and deployment and provide a standard unit for scheduling, scaling, and replacement. They do not remove environment differences or operational work, but they make many dependencies explicit and automatable.
03When to use it
Use containers when consistent packaging, process isolation, rapid replacement, or orchestration supports the delivery model. A simple process, managed function, platform service, or virtual machine may be more appropriate when container tooling adds no useful portability or control.
04How it works
- Describe the application filesystem, runtime, dependencies, entry point, and non-secret defaults in an image definition.
- Build an immutable image and identify it with a content digest or controlled version.
- Store and scan the image in a registry with provenance and access controls.
- Run the image with explicit configuration, secrets, network, storage, and resource limits.
- Replace containers with new image instances for deployment instead of modifying them in place.
- Observe process health and retain important data outside the disposable container filesystem.
05A practical example
A team packages an API and its language runtime in one image. Development, testing, and production run the same digest with different injected configuration; deployments replace instances gradually, while uploaded files remain in external object storage.
06Where it breaks
Containers share a kernel and are not the same isolation boundary as virtual machines. Images can contain vulnerabilities and become large or irreproducible. Stateful storage, networking, secrets, scheduling, and patching still require deliberate platform operation.
Common mistakes
- Using image and container as synonyms.
- Baking credentials or environment-specific configuration into an image.
- Writing important state only to the disposable container filesystem.
- Running without resource limits, image provenance, or a patching process.
07Sources
- Open Container Initiative Runtime SpecificationOpen Container Initiative · Open standardOpen Container Initiative Runtime Specification
- What Is a Container?Docker Docs · Official technical documentationWhat Is a Container?