

In general, Unix customs for representing and displaying modes will be used, including the use of octal numbers in this description.

Collectively, the permissions of a file or directory are its mode. Setting the sticky bit for a file has no effect. The sticky bit can be set on directories, preventing anyone except the superuser, directory owner or file owner from deleting or moving the files within the directory. For directories, there are no setuid or setgid bits directory as a simplification. In contrast to the POSIX model, there are no setuid or setgid bits for files as there is no notion of executable files. For directories, the r permission is required to list the contents of the directory, the w permission is required to create or delete files or directories, and the x permission is required to access a child of the directory. For files, the r permission is required to read the file, and the w permission is required to write or append to the file. The file or directory has separate permissions for the user that is the owner, for other users that are members of the group, and for all other users. Each file and directory is associated with an owner and a group. The Hadoop Distributed File System (HDFS) implements a permissions model for files and directories that shares much of the POSIX model. Running Applications in runC Containers.Running Applications in Docker Containers.
