dgstewart

For what it's worth, I have not observed this behavior since I changed my pinned cores from the last two cores of my system (CPU 22 - HT 46, CPU 23 - HT 47) to the first few cores of my system (CPU 1 - HT 25, CPU 2 - HT 26). Not sure if this is still the case, or ever was, but I remember being told specifically not to isolate Core 0 since the Unraid Host OS uses this for its related functions. To reiterate, my particular issue was that a NON-pinned and NON-privileged container, after some time of running normally, was getting assigned to the last thread on my system (HT 47) I can only speculate as to why this was happening. Hopefully this helps somebody and maybe confirms my procedure as a temporary solution.

I've noticed this behavior too, despite the last 2core/2threads of my system being isolated, one docker container in particular will exclusively sit on an isolated thread and keep it pinned at 100%. No amount of tinkering with privileged/unprivileged container settings has changed this. I have confirmed that the docker is not assigned to any cores/threads and is most certainly not assigned to these isolated cores.