Container

Container is an isolated environment exists in user space that use system resources allowed by #operating-system. It doesn’t rely on hardware virtualisation. Instead, it utilises the operating system virtualisation.

Because of this, container is more lightweight, has faster startup and uses less memory than 202204071131. However, since containers share the same underlying Kernel#, they are less secure than virtual machine.

Container’s lifetime is tie to its process which is running inside it. It will die as soon as the process finished its execution.

There are different types of container:

Technologies

In different operating system, containment implementation could vary.

References

Primer to Container Security, Linux Journal

Links to this page

macOS Hypervisor Technology

macOS does not have a default hypervisor driver. It usually relied on Oracle Virtual Machine to do most of the virtualisation. In order to run multiple #202202211633 inside macOS, it is necessary to install a third-party hypervisor toolkit.
Windows Containers

Windows has 2 types of #202202211633 available:
System Container

System #202202211633 simulate a full-fledge operating system, included the Kernel#, system libraries and the targeted application to be contained, on top the containment facilities provided by the underlying host kernel. It is quite similar to 202204071131 but used only the kernel facilities.
Server Templating

Server Templating tools are often used to set up an Immutable Infrastructure# using Virtual Machine (VM)# and Container# images. To modify the underlying infrastructure in demands of changing requirements, it can simply update the existing images without affecting other already running environment. #Infrastructure as Code (IaC) sometimes involves Server Templating.
Linux Container (LXC)

LXC is a user interface for Linux #containment features which included:
Application Container

Application #202202211633 provides an isolated environment for a single application. It is much more light-weight compare to 202204071117.
Ansible Execution Environment (EE)

EE is a #202202211633 image, commonly referred to as Universal Base Image, built by Ansible Builder that incorporates 202204300837#, libraries and core# (any version of it). It replaces the Python virtual environment (virtualenv). It could be run by #202204300954.

#container #operating-system