[6.6.1] Docker CPU Pinning Only using one core when CPU Isolation is on

This is by design of the kernel. See also Help on the CPU pinning page.

Quote

Do not select cores for containers which are isolated. By design a container will only use a single core (the lowest numbered core) when multiple isolated cores are selected. Usually this is not what a user wants when selecting multiple cores.

 

Edited October 5, 2018 by bonienl

Changed Status to Closed

Changed Priority to Other

On 10/4/2018 at 11:11 PM, bonienl said:

This is by design of the kernel. See also Help on the CPU pinning page.

 

Is there another way of wording the explanation that you quoted? I read the same thing under the help toggle when logged into the Web GUI, but for some reason it isn't clicking for me on how 'CPU Isolation works'.

 

Do you have a proposal how to improve?

15 minutes ago, bonienl said:

Do you have a proposal how to improve?

Under CPU isolation, remove all references to Docker.  Make it simple and state its to isolate cores so that VMs have exclusive access to it.  

 

While technically you can pin docker to an isolated core, it introduces complications and support headaches as to why it doesn't run on multiple cores. 

 

Additionally, per my original suggestion on the originating PR, don't allow containers to be pinned to isolated cores via the GUI.  Uber advanced users can still do it via extra parameters.

Edited November 8, 2018 by Squid