We’ve recently updated to Nomad 1.1 to take advantage of the core reservation feature but we’ve noticed what we think is unexpected behaviour in docker. For a docker driver job that specifies “cores: 2” how should that be reflected in CpuShares and CpusetCpus values for that container? We’re seeing the value of CpuShares increase and decrease by a factor of the jobs cores value while the CpusetCpu value stays at 0.
How does Nomad pin the jobs container to the reserved CPU resource? Are we looking in the wrong place?