A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://developer.hashicorp.com/nomad/docs/deploy/task-driver/raw_exec below:

Raw Fork/Exec task driver | Nomad

Configure the Raw Fork/Exec task driver

Name: raw_exec

The raw_exec driver is used to execute a command for a task without any isolation. Further, the task is started as the same user as the Nomad process. As such, it should be used with extreme care and is disabled by default.

The raw_exec driver implements the following capabilities.

Feature Implementation nomad alloc signal true nomad alloc exec true filesystem isolation none network isolation host, group volume mounting none

The raw_exec driver can run on all supported operating systems. For security reasons, it is disabled by default. To enable raw exec, the Nomad client configuration must explicitly enable the raw_exec driver in the plugin's options:

plugin "raw_exec" {
  config {
    enabled = true
  }
}

Nomad versions before v0.9 use the following client configuration. This configuration is also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:

client {
  options = {
    "driver.raw_exec.enable" = "1"
  }
}
config {
  denied_host_uids = "0,10-15,22"
}
config {
  denied_host_gids = "2,4-8"
}
config {
  denied_envvars = ["AWS_SECRET_KEY", "*_TOKEN"]
}

Note: client configuration options will soon be deprecated. Please use plugin options instead. See the plugin block documentation for more information.

The raw_exec driver will set the following client attributes:

The raw_exec driver provides no filesystem isolation.

If the launched process creates a new process group, it is possible that Nomad will leak processes on shutdown unless the application forwards signals properly. Nomad will not leak any processes if cgroups are being used to manage the process tree. Cgroups are used on Linux when Nomad is being run with appropriate privileges, and the cgroup system is mounted.

If the cluster is configured with memory oversubscription enabled, a task using the raw_exec driver can be configured to have no maximum memory limit by setting memory_max = -1.

resources {
  cpu        = 500
  memory     = 128
  memory_max = -1 # no limit
}

Use the raw_exec driver in a job.


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