From 41e6e6ad350920700615a5387f7988711293f989 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Fri, 3 Feb 2017 11:33:09 -0800 Subject: [PATCH] config-linux: Drop the default-filesystem section Users who need these mounts would have to explicitly set them up in their configuration (as runtime-tools continues to do [1]) if they wanted to guarantee their presence. Users who don't need them can omit them from their configuration. I don't see how keeping a SHOULD-strength runtime requirement helps either of those workflows. [1]: https://github.com/opencontainers/runtime-tools/pull/24 Signed-off-by: W. Trevor King --- config-linux.md | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/config-linux.md b/config-linux.md index 404072f7b..9a1f50333 100644 --- a/config-linux.md +++ b/config-linux.md @@ -3,20 +3,6 @@ This document describes the schema for the [Linux-specific section](config.md#platform-specific-configuration) of the [container configuration](config.md). The Linux container specification uses various kernel features like namespaces, cgroups, capabilities, LSM, and filesystem jails to fulfill the spec. -## Default Filesystems - -The Linux ABI includes both syscalls and several special file paths. -Applications expecting a Linux environment will very likely expect these file paths to be setup correctly. - -The following filesystems SHOULD be made available in each container's filesystem: - -| Path | Type | -| -------- | ------ | -| /proc | [procfs](https://www.kernel.org/doc/Documentation/filesystems/proc.txt) | -| /sys | [sysfs](https://www.kernel.org/doc/Documentation/filesystems/sysfs.txt) | -| /dev/pts | [devpts](https://www.kernel.org/doc/Documentation/filesystems/devpts.txt) | -| /dev/shm | [tmpfs](https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt) | - ## Namespaces A namespace wraps a global system resource in an abstraction that makes it appear to the processes within the namespace that they have their own isolated instance of the global resource.