User Identity in Container
In docker, as well as in Kubernetes, the default for running containers is running as 'root'. The implication of running as root is that processes running within the container have enough permissions to change anything on the machine itself.
This gives a lot of power to containers but does not sit well with modern security standards. Specifically enterprise security. To overcome that:
- Kubernetes provides a mechanism called PodSecurityPolicy (PSP) to control container access.
- OpenShift provides control over container access using Security Context Constraints (SCC).
Run:AI supports both PSP and SCC. This support is at the cluster installation level.
The identity of the user in the container determines its access to cluster resources. For example: network file storage solutions typically use this identity to determine the container's access to network volumes.
The Run:AI Command-line interface provides flags to control user identity within the container and to disable root access capabilities.
There are two runai submit flags which control user identity at the Researcher level:
- The flag
--run-as-userstarts the container with a specific user. The user is the current Linux user or if connected via LDAP, it can be the Linux UID/GID which is stored in the organization's directory.
- The flag
--prevent-privilege-escalationprevents the container from elevating its own privileges into root (e.g. running
sudoor changing system files.). This flag is not relevant when using PSP or SCC.
Note, that these flags are voluntary. They are not enforced by the system.
It is possible to set these flags as a cluster-wide default for the Run:AI CLI, such that all CLI users will be limited to non-root containers.
Setting a Cluster-Wide Default¶
Save the following in a file (cluster-config.yaml)
apiVersion: v1 data: config: | enforceRunAsUser: true enforcePreventPrivilegeEscalation: true kind: ConfigMap metadata: name: cluster-config namespace: runai labels: runai/cluster-config: "true"
kubectl apply -f cluster-config.yaml
Preventing privilege escalation at the cluster level limits non-root for all Run:AI CLI users. However, it does not prevent users or malicious actors from starting containers directly via Kubernetes API (e.g. via YAML files). To fully secure the system use PSP or work with OpenShift SCC.
Creating a Temporary Home Directory¶
For containers to run as a specific user, the user needs to have a pre-created home directory within the image. This can be a daunting IT task.
To overcome this, Run:AI provides an additional flag
--create-home-dir. Adding this flag creates a temporary home directory for the user within the container.
- Data saved in this directory will not be saved when the container exits.
- This flag is set by default to true when the
--run-as-userflag is used, and false if not.