Understanding General Process-Sharing Resources
In a generic computing environment, processes share resources, which can lead to disputes and resource management difficulties.
Consider several processes executing on a host machine with no isolation. These programs may unintentionally interact with one another, resulting in resource congestion, security risks, and challenges in managing dependencies.
In this case, processes share the same namespace, resulting in a lack of separation and independence. Resource conflicts, such as two processes attempting to access the same memory location or a competing file access, can cause unstable and unexpected behavior.
What is Docker Namespaces?
Namespaces have been part of the Linux kernel since around 2002, with more functionality and namespace types introduced over time. Real container functionality was added to the Linux kernel in 2013, however. This is what makes namespaces useful and popular. Namespaces enable you to create an isolated environment in which the container only knows what it can see because it is only in a certain namespace. When you begin a container, Docker creates a set of namespaces for it, and each container has its own distinct set of namespaces.