https://bugzilla.redhat.com/show_bug.cgi?id=1046469
Joe Mario jmario@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |POST CC| |jmario@redhat.com Resolution|CURRENTRELEASE |--- Keywords| |Reopened
--- Comment #3 from Joe Mario jmario@redhat.com ---
Closing as fixed in current release. Reopen if it still happens.
Re-opening. It's still happening with a RHEL7.2 host, a RHEL7.2 container and a docker-1.8.2-2.el7. The Dockerfile contains systemd, if that matters.
Steps to reproduce: 1) Create two containers using: docker run -d -v /sys/fs/cgroup:/sys/fs/cgroup:ro --privileged test /sbin/init docker run -d -v /sys/fs/cgroup:/sys/fs/cgroup:ro --privileged test /sbin/init
2) Start two containers: docker exec -it <container-1-id> bash docker exec -it <container-2-id> bash
3) Run top on the bare metal host. You should see an agetty process burning up one cpu:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 73529 root 20 0 110004 680 660 R 99.7 0.0 10:53.98 agetty
Note, this problem does not occur if, when creating the containers, I replace the "--privileged" flag with "--security-opt label:disable --cap-add SYS_ADMIN"
Joe