NamespaceWhat it isolatesWhat the process seesPIDProcess IDsOwn process tree, starts at PID 1MountFilesystem mount pointsOwn mount table, can have different rootNetworkNetwork interfaces, routingOwn interfaces, IP addresses, portsUserUID/GID mappingCan be root inside, nobody outsideUTSHostnameOwn hostnameIPCSysV IPC, POSIX message queuesOwn shared memory, semaphoresCgroupCgroup root directoryOwn cgroup hierarchyTimeSystem clocks (monotonic, boot)Own system uptime and clock offsetsNamespaces are what Docker containers use. When you run a container, it gets its own PID namespace (cannot see host processes), its own mount namespace (own filesystem view), its own network namespace (own interfaces), and so on.
Москвичи пожаловались на зловонную квартиру-свалку с телами животных и тараканами18:04
。关于这个话题，搜狗输入法下载提供了深入分析
For running trusted code that you wrote and reviewed, Docker with a seccomp profile is probably fine. The isolation is against accidental interference, not adversarial escape.，更多细节参见同城约会
"tengu_brass_pebble": false,