Fix review comments.

hashicorp · Jul 15, 2020 · 46211fd · 46211fd
1 parent ee616f9
commit 46211fd
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/drivers/docker/driver.go b/drivers/docker/driver.go
@@ -820,7 +820,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
 	}
 

diff --git a/website/pages/docs/drivers/docker.mdx b/website/pages/docs/drivers/docker.mdx
@@ -74,8 +74,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 {