Merge pull request #1409 from apelisse/add-privileged-link
Points to documentation about running privileged containers
This commit is contained in:
@@ -126,9 +126,10 @@ Watch out when using this type of volume, because:
|
|||||||
behave differently on different nodes due to different files on the nodes
|
behave differently on different nodes due to different files on the nodes
|
||||||
* when Kubernetes adds resource-aware scheduling, as is planned, it will not be
|
* when Kubernetes adds resource-aware scheduling, as is planned, it will not be
|
||||||
able to account for resources used by a `hostPath`
|
able to account for resources used by a `hostPath`
|
||||||
* the directories created on the underlying hosts are only writable by root, you either need
|
* the directories created on the underlying hosts are only writable by root. You
|
||||||
to run your process as root in a privileged container or modify the file permissions on
|
either need to run your process as root in a
|
||||||
the host to be able to write to a `hostPath` volume
|
[privileged container](/docs/user-guide/security-context) or modify the file
|
||||||
|
permissions on the host to be able to write to a `hostPath` volume
|
||||||
|
|
||||||
#### Example pod
|
#### Example pod
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user