------- Comment From [email protected] 2016-03-02 01:41 EDT------- The upstream fix should have fixed this issue:
docker container is bound to some cpuset and that is not honoured by the system. This can be verified by checking the corresponding cpuset cgroup of docker container in the host. The upstream fix will not fix this issue: /proc/cpuinfo showing what is the container affinity. /proc/cpuinfo shows all the cpus available in the system but it does not have anything to do with affinity of container. Hope this is clear -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1435571 Title: docker: docker run --cpuset is not having any effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435571/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
