github.com/iqoqo/nomad@v0.11.3-0.20200911112621-d7021c74d101/website/pages/docs/drivers/index.mdx (about)

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