Unable to dynamically change cpuset.cpus for container image

Solution In Progress - Updated -

Issue

After "hot-adding" CPUs to an Atomic host on reboot, containers previously created have only assigned the original CPU list in their cpuset.cpus file, and do not make use of the new CPUs

Environment

  • Red Hat Enterprise Linux Atomic Host 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.