Unable to dynamically change cpuset.cpus for container image

Solution In Progress - Updated -


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


  • Red Hat Enterprise Linux Atomic Host 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content