Containerization (computing) 📖 Wikipedia

In software engineering, containerization is operating-system-level virtualization or application-level virtualization over multiple resources so that software applications can run in isolated user spaces called containers in any cloud or non-cloud environment, regardless of type or vendor.^[1] The term "container" has different meanings in different contexts, and it is important to ensure that the intended definition aligns with the audience's understanding.^[2][3]

Each container is basically a fully functional and portable cloud or non-cloud computing environment surrounding the application and keeping it independent of other environments running in parallel.^[4] Individually, each container simulates a different software application and runs isolated processes^[5] by bundling related configuration files, libraries and dependencies.^[6] But, collectively, multiple containers share a common operating system kernel (OS).^[7]

In recent times, containerization technology has been widely adopted by cloud computing platforms like Amazon Web Services, Microsoft Azure, Google Cloud Platform, and IBM Cloud.^[8] Containerization has also been pursued by the U.S. Department of Defense as a way of more rapidly developing and fielding software updates, with first application in its F-22 air superiority fighter.^[9]

The concept of containerization in computing originated from early operating system–level isolation mechanisms. One of the earliest implementations was the chroot system call introduced in Version 7 Unix in 1979, which changed the apparent root directory for a process and its children, providing a basic form of filesystem isolation.^[10]

In the early 2000s, more advanced forms of operating system–level virtualization were developed. FreeBSD introduced "jails" in 2000, which extended isolation by restricting processes to a subset of system resources. Around the same time, Solaris introduced "zones" (also known as Solaris Containers), providing similar capabilities with resource management and isolation features.

Linux later incorporated comparable functionality through kernel features such as namespaces and control groups (cgroups), which enabled isolation of process IDs, network stacks, filesystems, and resource allocation. These features formed the foundation for Linux Containers (LXC), which provided a userspace interface for managing containers.

The widespread adoption of containerization accelerated with the release of Docker in 2013, which introduced a standardized format for packaging applications and their dependencies, along with tooling for image distribution and container management.

• OS containers
• Application containers

• Because of the shared OS, security threats can affect the whole containerized system.
• In containerized environments, security scanners generally protect the OS, but not the application containers, which adds unwanted vulnerability.

Container orchestration or container management is mostly used in the context of application containers.^[11] Implementations providing such orchestration include Kubernetes and Docker swarm.

Container clusters need to be managed. This includes functionality to create a cluster, to upgrade the software or repair it, balance the load between existing instances, scale by starting or stopping instances to adapt to the number of users, to log activities and monitor produced logs or the application itself by querying sensors. Open-source implementations of such software include OKD and Rancher. Quite a number of companies provide container cluster management as a managed service, like Alibaba, Amazon, Google, and Microsoft.

This software-engineering-related article is a stub. You can help Wikipedia by adding missing information.

• v
• t
• e