2015-09-12 00:01:02 +00:00
|
|
|
---
|
2020-02-06 23:45:31 +00:00
|
|
|
layout: docs
|
|
|
|
|
page_title: Task Drivers
|
|
|
|
|
description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
|
2015-09-12 00:01:02 +00:00
|
|
|
---
|
|
|
|
|
|
2015-09-20 22:31:33 +00:00
|
|
|
# Task Drivers
|
2015-09-12 00:01:02 +00:00
|
|
|
|
2015-09-20 22:31:33 +00:00
|
|
|
Task drivers are used by Nomad clients to execute a task and provide resource
|
|
|
|
|
isolation. By having extensible task drivers, Nomad has the flexibility to
|
|
|
|
|
support a broad set of workloads across all major operating systems.
|
2015-09-12 00:01:02 +00:00
|
|
|
|
2019-01-29 20:53:05 +00:00
|
|
|
Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
|
|
|
|
|
flexibility to introduce their own drivers without having to recompile Nomad.
|
|
|
|
|
You can view the [plugin stanza][plugin] documentation for examples on how to
|
|
|
|
|
use the `plugin` stanza in Nomad's client configuration. Note that we have
|
|
|
|
|
introduced new syntax when specifying driver options in the client configuration
|
|
|
|
|
(see [docker][docker_plugin] for an example). Keep in mind that even though all
|
|
|
|
|
built-in drivers are now plugins, Nomad remains a single binary and maintains
|
2020-02-06 23:45:31 +00:00
|
|
|
backwards compatibility except with the `lxc` driver.
|
2019-01-29 20:53:05 +00:00
|
|
|
|
|
|
|
|
The list of supported task drivers is provided on the left of this page. Each
|
|
|
|
|
task driver documents the configuration available in a [job
|
2020-02-06 23:45:31 +00:00
|
|
|
specification](/docs/job-specification), the environments it can be
|
2019-01-29 20:53:05 +00:00
|
|
|
used in, and the resource isolation mechanisms available.
|
2015-09-12 00:01:02 +00:00
|
|
|
|
2019-05-07 17:40:22 +00:00
|
|
|
For details on authoring a task driver plugin, please refer to the [plugin
|
|
|
|
|
authoring guide][plugin_guide].
|
2019-01-29 20:53:05 +00:00
|
|
|
|
2019-09-03 22:19:46 +00:00
|
|
|
Task driver resource isolation is intended to provide a degree of separation of
|
|
|
|
|
Nomad client CPU / memory / storage between tasks. Resource isolation
|
|
|
|
|
effectiveness is dependent upon individual task driver implementations and
|
2019-09-04 00:38:32 +00:00
|
|
|
underlying client operating systems. Task drivers do include various
|
|
|
|
|
security-related controls, but the Nomad client to task interface should not be
|
2019-09-03 22:19:46 +00:00
|
|
|
considered a security boundary. See the [access control guide][acl_guide] for
|
|
|
|
|
more information on how to protect Nomad cluster operations.
|
|
|
|
|
|
2020-03-20 22:24:56 +00:00
|
|
|
[plugin]: /docs/configuration/plugin
|
2020-02-06 23:45:31 +00:00
|
|
|
[docker_plugin]: /docs/drivers/docker#client-requirements
|
|
|
|
|
[plugin_guide]: /docs/internals/plugins
|
2020-09-29 16:48:32 +00:00
|
|
|
[acl_guide]: https://learn.hashicorp.com/collections/nomad/access-control
|
