Quoting Trent W. Buck (trentb...@gmail.com):
Serge E. Hallyn serge.hal...@canonical.com
writes:
Quoting Trent W. Buck (t...@cybersource.com.au):
I encountered, isolated, and worked around this issue.
Symptom: gettys don't start in the container. runlevel(8) reports
unknown instead
I had a bash process in a container go haywire and consume 100% of a
core yesterday. It made me think:
Is there a way to cap the AMOUNT of CPU a container can use?
I realize I can assign a container to a specific subset of cores
(cpuset), and change how free CPU is divvied up between
