Introduction
There have been inquiries about having CPUs pinned as an option in docker driver.
Problem & Cause
One of the inquiries is recorded in GH-2303 with our response: “This is likely not a feature we will support/expose to the user as multiple jobs running on the same node could have detrimental performance effects if they have the same cpu pinning.”
Nomad will honor the spirit of the intent, but the more obscure/specific the driver flags are, the less likely they are to be added to the scheduler.
Solution
A recommended alternative would be to use constraint or affinity to achieve more restrictive placement within a group or class of resources.