I am wondering what exactly the “Namespaces support” feature in the Linux kernel means. I am using kernel 3.11.1 (the newest stable kernel at this time).

If I decide to disable it, will I notice any change on my system?

And in case somebody decides to make use of namespaces, is it enough to just compile NAMESPACES=Y in the kernel, or does he need userspace tools as well?

  • 5
    Namespaces are explained fairly well here: lwn.net/Articles/531114 (not an answer, because I'm not really answering your questions—I'm pointing you to a pile of text) – derobert Sep 24 '13 at 15:17

In a nutshell, namespaces provide a way to build a virtual Linux system inside a larger Linux system. This is different from running a virtual machine that runs as an unprivileged process: the virtual machine appears as a single process in the host, whereas processes running inside a namespace are still running on the host system.

A virtual system running inside a larger system is called a container. The idea of a container is that processes running inside the container believe that they are the only processes in the system. In particular, the root user inside the container does not have root privileges outside the container (note that this is only true in recent enough versions of the kernel).

Namespaces virtualize one feature at a time. Some examples of types of namespaces are:

  • User namespaces — this allows processes to behave as if they were running as different users inside and outside the namespace. In particular, processes running as UID 0 inside the namespace have superuser privileges only with respect to processes running in the same namespace.
    Since Linux kernel 3.8, unprivileged users can create user namespaces. This allows an ordinary user to make use of features that are reserved to root (such as changing routing tables or setting capabilities).
  • PID namespaces — processes inside a PID namespace cannot kill or trace processes outside that namespace.
  • Mount namespaces — this allows processes to have their own view of the filesystem. This view can be a partial view, allowing some pieces of the filesystem to be hidden and pieces to be recomposed so that directory trees appear in different places. Mount namespaces generalize the traditional Unix feature chroot, which allows processes to be restricted to a particular subtree.
  • Network namespaces — allow separation of networking resources (network devices) and thus enhance isolation of processes.

Namespaces rely on the kernel to provide isolation between namespaces. This is quite complicated to get right, so there may still be security bugs lying around. The risk of security bugs would be the primary reason not to enable the feature. Another reason not to enable it would be when you're making a small kernel for an embedded device. In a general-purpose kernel that you'd install on a typical server or workstation, namespaces should be enabled, like any other mature kernel feature.

There are still few applications that make use of namespaces. Here are a few:

  • LXC is well-established. It relies on cgroups to provide containers.
  • virt-sandbox is a more recent sandboxing project.
  • Recent versions of Chromium also use namespaces for sandboxing where available.
  • The uWSGI framework for clustered applications uses namespaces for improved sandboxing.

See the LWN article series by Michael Kerrisk for more information.

| improve this answer | |

Linux kernel namespace is a concept used for isolating a group of processes from others with respect to access to a system resource. For example two different PID namespaces may contain processes with identical PIDs but completely different process image. They are often used in OS-level virtualisation, in which a single kernel is simultaneously running various operating systems - all have to be Linux based (because they share the kernel, obviously), but may be different distributions and versions. See for example LXC.

You may notice disabling it for example on systemd-based systems, since systemd is able to use namespaces for its container feature. Hence a lot depends on what distribution you are using and what you intend to do with the system.

As with almost every kernel feature, you definitely need some sort of user space programs - even if you talked to the kernel through special files (I'm not sure you can), it's usually much better idea to rely on specialized tools, since they offer fore friendly API.

| improve this answer | |

To give an example of namespace usage, in SELinux (MLS or Strict) enabled systems. Namespace is typically used to create individual /tmp and or /home directories for each user. Those directories are visible only to: the user, users with the same label, the kernel and users with privileged access. The namespace-ed /tmp directory gets labeled by SELinux-MLS to match the user's SELinux-MLS label. In this scenario the /tmp directory that the user sees may really be mounted somewhere other than /tmp (/var/user-tmp). The user however only sees /tmp with the files that are created due to the user's activity. the user will never see any files in /tmp that are the product of other users.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.