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.
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.
The Nomad binary contains several bundled task drivers. We also support additional task driver plugins that you may install separately.
Refer to each task driver's page for detailed usage.
Refer to Configure Nomad task drivers for task driver plugin configuration details.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4