github.com/anth0d/nomad@v0.0.0-20221214183521-ae3a0a2cad06/website/content/docs/drivers/index.mdx (about)

     1  ---
     2  layout: docs
     3  page_title: Task Drivers
     4  description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
     5  ---
     6  
     7  # Task Drivers
     8  
     9  Task drivers are used by Nomad clients to execute a task and provide resource
    10  isolation. By having extensible task drivers, Nomad has the flexibility to
    11  support a broad set of workloads across all major operating systems.
    12  
    13  Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
    14  flexibility to introduce their own drivers without having to recompile Nomad.
    15  You can view the [plugin stanza][plugin] documentation for examples on how to
    16  use the `plugin` stanza in Nomad's client configuration. Note that we have
    17  introduced new syntax when specifying driver options in the client configuration
    18  (see [docker][docker_plugin] for an example). Keep in mind that even though all
    19  built-in drivers are now plugins, Nomad remains a single binary and maintains
    20  backwards compatibility except with the `lxc` driver.
    21  
    22  The list of supported task drivers is provided on the left of this page. Each
    23  task driver documents the configuration available in a [job
    24  specification](/docs/job-specification), the environments it can be
    25  used in, and the resource isolation mechanisms available.
    26  
    27  For details on authoring a task driver plugin, please refer to the [plugin
    28  authoring guide][plugin_guide].
    29  
    30  Task driver resource isolation is intended to provide a degree of separation of
    31  Nomad client CPU / memory / storage between tasks. Resource isolation
    32  effectiveness is dependent upon individual task driver implementations and
    33  underlying client operating systems. Task drivers do include various
    34  security-related controls, but the Nomad client to task interface should not be
    35  considered a security boundary. See the [access control guide][acl_guide] for
    36  more information on how to protect Nomad cluster operations.
    37  
    38  [plugin]: /docs/configuration/plugin
    39  [docker_plugin]: /docs/drivers/docker#client-requirements
    40  [plugin_guide]: /docs/concepts/plugins
    41  [acl_guide]: https://learn.hashicorp.com/collections/nomad/access-control