fix a couple more links
This commit is contained in:
parent
ba72fc57c2
commit
569bead286
|
@ -10,7 +10,7 @@ description: The Exec task driver is used to run binaries using OS isolation pri
|
|||
Name: `exec`
|
||||
|
||||
The `exec` driver is used to simply execute a particular command for a task.
|
||||
However, unlike [`raw_exec`](raw_exec) it uses the underlying isolation
|
||||
However, unlike [`raw_exec`](/docs/drivers/raw_exec) it uses the underlying isolation
|
||||
primitives of the operating system to limit the task's access to resources. While
|
||||
simple, since the `exec` driver can invoke any command, it can be used to call
|
||||
scripts or other wrappers which provide higher level features.
|
||||
|
@ -32,7 +32,7 @@ The `exec` driver supports the following configuration in the job spec:
|
|||
|
||||
- `command` - The command to execute. Must be provided. If executing a binary
|
||||
that exists on the host, the path must be absolute and within the task's
|
||||
[chroot](exec#chroot). If executing a binary that is downloaded from
|
||||
[chroot](#chroot). If executing a binary that is downloaded from
|
||||
an [`artifact`](/docs/job-specification/artifact), the path can be
|
||||
relative from the allocations's root directory.
|
||||
|
||||
|
|
|
@ -32,7 +32,7 @@ A device plugin is long-lived. Nomad will ensure that one instance of the plugin
|
|||
running. If the plugin crashes or otherwise terminates, Nomad will launch another
|
||||
instance of it.
|
||||
|
||||
However, unlike [task drivers](task-drivers), device plugins do not currently
|
||||
However, unlike [task drivers](/docs/internals/plugins/task-drivers), device plugins do not currently
|
||||
have an interface for persisting state to the Nomad client. Instead, the device
|
||||
plugin API emphasizes fingerprinting devices and reporting their status. After
|
||||
helping to provision a task with a scheduled device, a device plugin does not
|
||||
|
|
Loading…
Reference in New Issue