Exec2 Task Driver

Name: exec2

The exec2 driver is used to execute a command for a task. It offers a security model optimized for running 'ordinary' processes with very low startup times and minimal overhead in terms of CPU, disk, and memory utilization. The exec2 driver leverages kernel features such as the Landlock LSM, cgroups v2, and the unshare system utility.

Source is on GitHub

Installation

You can download a precompiled binary and verify the binary using the available SHA-256 sums. After downloading nomad-driver-exec2 driver, unzip the package. Make sure that the nomad-driver-exec2 binary is available on your plugin_dir path, specified by the client's config file, before continuing with the other guides.

Install the required packages.

$ sudo apt-get update && \  sudo apt-get install wget gpg coreutils

Add the HashiCorp [GPG key][gpg-key].

$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg

Add the official HashiCorp Linux repository.

$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list

Update and install.

$ sudo apt-get update && sudo apt-get install nomad-driver-exec2

Install yum-config-manager to manage your repositories.

$ sudo yum install -y yum-utils

Use yum-config-manager to add the official HashiCorp Linux repository.

$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo

Install.

$ sudo yum -y install nomad-driver-exec2

Usage

The example below is a short demonstration of what a task making use of the exec2 task driver looks like:

job "http" {  group "web" {    task "python" {      driver = "exec2"      config {        command = "python3"        args    = ["-m", "http.server", "8080", "--directory", "${NOMAD_TASK_DIR}"]        unveil  = ["r:/etc/mime.types"]      }    }  }}

Client Requirements

The exec2 task driver is not built into Nomad. It must be downloaded onto the client host in the configured plugin directory.

Linux 5.15+
Cgroups v2 enabled
Landlock LSM enabled
Commands nsenter and unshare
Nomad client running as root

Capabilities

The exec2 task driver implements the following driver capabilities

Feature	Implementation
`nomad alloc signal`	true
`nomad alloc exec`	false
filesystem isolation	unveil
network isolation	host, group, none
volume mounting	false

Concepts

Filesystem Isolation

landlock

The exec2 task driver makes use of go-landlock for providing filesystem isolation, making the host filesystem unreachable except where explicitly allowed.

By default a task is enabled to access its task directory and its shared alloc directory. The paths to these directories are accessible by reading the environment variables $NOMAD_TASK_DIR and $NOMAD_ALLOC_DIR respectively.

A file access mode must also be specified when granting additional filesystem access to a path. This is done by prefix the path with 'r', 'w', 'x', and/or 'c' indicating read, write, executable, and create permissions, respectively. e.g.,

r:/srv/www - read-only access to `/srv/www`
rwc:/tmp - read, write, and create files in `/tmp`
rx:/opt/bin/application - read and execute a specific application
wc:/var/log - write and create files in `/var/log`

This style of permission control is modeled after the unveil system call pioneered by the OpenBSD project. In configuration parameters we refer to "unveil"-ing of filesystem paths as exec2 is leveraging landlock to emulate the semantics of unveil.

dynamic workload users

While landlock prevents tasks from accessing the host filesystem, Nomad 1.8 introduces dynamic workload users which enable tasks to be run as a UID/GID that is not assigned to any user. This provides protection from non-root users getting access inside the task and allocation directories created for the task.

To make use of a dynamic workload user, simply leave the user field blank in the task definition of an exec2 task.

Resource Isolation

Similar to exec and other container runtimes, exec2 makes use of cgroups for limiting the amount of CPU and RAM a task may consume.

Configuration

Plugin Configuration

The default plugin configuration is shown below. System default paths are enabled, but nothing else. These default paths enable basic functionality like reading system TLS certificates, executing programs in /bin, /usr/bin, and accessing system shared object files. The exact set of paths is system dependent, and can be disabled or customized in plugin config.

The default set of paths are listed below. These paths are enabled only if they are found to exist at the time of the task launching.

shared objects

rx:/librx:/lib64rx:/usr/librx:/usr/libexecrx:/usr/local/librx:/usr/local/lib64r:/etc/ld.so.confr:/etc/ld.so.cacher:/etc/ld.so.conf.d

io, common

rwc:/tmprw:/dev/nullr:/dev/zeror:/dev/fdrw:/dev/stdinrw:/dev/stdoutr:/dev/urandomw:/dev/logr:/usr/share/localer:/proc/self/cmdliner:/usr/share/zoneinfor:/usr/share/common-licensesr:/proc/sys/kernel/ngroups_maxr:/proc/sys/kernel/cap_last_capr:/proc/sys/vm/overcommit_memory

dns

r:/etc/hostsr:/hostnamer:/etc/servicesr:/etc/protocolsr:/etc/resolv.conf

certificates

r:/etc/ssl/certsr:/etc/pki/tls/certsr:/etc/ssl/ca-bundle.pemr:/etc/pki/tls/cacert.pemr:/etc/pki/ca-trust-extracted/pem/tls-ca-bundle.pemr:/etc/ssl/cert.pem

Additional allowable paths can be specified at the plugin level, which applies to all tasks making use of the exec2 task driver, or at the task level, which will apply specifically to each task.

plugin "nomad-driver-exec2" {  config {    unveil_defaults = true    unveil_paths    = []    unveil_by_task  = false  }}

unveil_defaults - (default: true) - enable or disable default system paths useful for running basic commands
unveil_paths - (default: []) - a list of filesystem paths with permissions to grant all tasks
```
unveil_paths = ["rx:/opt/bin", "r:/srv/certs"]
```
unveil_by_task - (default: false) - enable or disable job submitters to specify additional filesystem path access within task config

Task Configuration

config

Task configuration for an exec2 task includes setting a command, args for the command, and additional unveil filesystem paths if unveil_by_task is enabled in plugin configuration.

config {    command = "/usr/bin/cat"    args    = ["/etc/os-release"]    unveil  = ["r:/etc/os-release"]}

command - (string: required) - command to run
args - (list(string): optional) - list of arguments to provide to command
unveil - (list(string): optional) - list of additional filesystem paths to provide access to the task (requires unveil_by_task in plugin config).

cpu

Tasks are limited in CPU resources by setting the cpu or cores values in the task resources block.

cpu - (default: 100) - limits the CPU bandwidth allowable for the task to make use of in MHz, may not be used with cores.
cores - (int: optional) - specifies the number of CPU cores to reserve specifically for the task, may not be used with cpu

memory

Tasks are limited in memory resources by setting memory and optionally the memory_max values in the task resources block.

Node Attributes

When installed, the exec2 plugin provides the following node attributes which can be used as constraints when authoring jobs.

driver.exec2.unveil.defaults    = truedriver.exec2.unveil.tasks       = true