luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Fix review comments.

This commit is contained in:
Shishir Mahajan 2020-06-26 11:14:53 -07:00
parent 9192100d4e
commit 572c398187
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
drivers/docker/driver.go
View File

@ -826,7 +826,6 @@ func (d *Driver) createContainerConfig(task *drivers.TaskConfig, driverConfig *T
// This translates to docker create/run --cpuset-cpus option.
// --cpuset-cpus limit the specific CPUs or cores a container can use.
if driverConfig.CPUSetCPUs != "" {
logger.Debug(fmt.Sprintf("Setting CPUSetCPUs to %s", driverConfig.CPUSetCPUs))
hostConfig.CPUSetCPUs = driverConfig.CPUSetCPUs
}

7
website/pages/docs/drivers/docker.mdx
View File

@ -78,8 +78,13 @@ The `docker` driver supports the following configuration in the job spec. Only
}
```
- `cpuset_cpus` - (Optional) CPUs in which to allow execution (0-3, 0,1).
Limit the specific CPUs or cores a container can use. A comma-separated list
or hyphen-separated range of CPUs a container can use, if you have more than
one CPU. The first CPU is numbered 0. A valid value might be 0-3 (to use the
first, second, third, and fourth CPU) or 1,3 (to use the second and fourth CPU).
Limit the specific CPUs or cores a container can use. A comma-separated list or hyphen-separated range of CPUs a container can use, if you have more than one CPU. The first CPU is numbered 0. A valid value might be 0-3 (to use the first, second, third, and fourth CPU) or 1,3 (to use the second and fourth CPU).
Note: `cpuset_cpus` pins the workload to the CPUs but doesn't give the workload
exclusive access to those CPUs.
```hcl
config {