- Minor
I tried to fix this odd issue for about an hour earlier with no success. Unraid is setting CPU pinning for containers even after I remove these definitions. I've tried ensuring that there's nothing set under "Settings > CPU Pinning" for any docker containers, removing a container/image and recreating from a template that doesn't contain the `--cpuset-cpus` param (NOTE: there needs to be an inline code option here, not just code block), rebooting, etc.
For example, I'll start off with no CPU Pinning defined for my Docker containers in settings
If I go to one of the problem containers (pretty much all of them I think), it will have a `--cpuset-cpus` param set that was not there upon creation.
If I delete the contents of 'Extra Parameters:', hit 'Apply', and go back to edit the container, the `--cpuset-cpus` param is back again. Even if I turn on template authoring mode, save the changes and create it from my template, it magically reappears. Pretty annoying and kind of backwards considering the param was supposed to be deprecated in favor of the GUI pinning options.