The resource isolation of docker uses the () feature of Linux

Question

Options

• Anamespace

• A
  100% (50)

Explanation

Option A is correct because Docker relies on Linux namespaces to provide process-level isolation between containers. Namespaces partition global kernel resources - such as process IDs (PID), network interfaces (NET), mount points (MNT), inter-process communication (IPC), hostnames (UTS), and user IDs (USER) - so that each container operates in its own isolated view of the system, unaware of resources belonging to other containers or the host. There are no distractors in this question since only one option is provided, but it is worth noting that cgroups (control groups) is a related but distinct Linux feature that handles resource limiting (CPU, memory, I/O) rather than isolation - a common point of confusion.

Memory tip: Think of a namespace as a "named bubble" - each container lives inside its own bubble where it cannot see outside, just as a name in one namespace does not conflict with the same name in another.

No community discussion yet for this question.