Nomad
Use Nomad task drivers in jobs
Nomad's bundled task drivers integrate with the host OS to run job tasks in isolation. Review job usage for the Docker, Isolated Fork/Exec, Java, QEMU, and Raw Fork/Exec task drivers.
Introduction
Nomad clients use task drivers to execute a task and provide resource isolation. Extensible task drivers provide Nomad the flexibility to support a broad set of workloads across all major operating systems.
Task driver resource isolation provides a degree of separation for Nomad's client CPU, memory, and storage between tasks. Resource isolation effectiveness depends upon individual task driver implementations and underlying client operating systems. Task drivers include various security-related controls but do not use the Nomad client-to-task interface as a security boundary. Refer to the access control guide for more information on how to protect Nomad cluster operations.
Nomad task drivers
The Nomad binary contains several bundled task drivers. We also support additional task driver plugins that you may install separately.
Bundled with Nomad | Plugins |
---|---|
Docker | Exec2 |
Isolated Fork/Exec | Podman |
Java | Virt |
QEMU | |
Raw Fork/Exec |
Refer to each task driver's page for detailed usage.
Configure task driver plugins
Refer to Configure Nomad task drivers for task driver plugin configuration details.