https://bugzilla.redhat.com/show_bug.cgi?id=1046469
--- Comment #11 from Joe Mario jmario@redhat.com --- Here's one workaround for this. Sharing what I've learned.
Adding the following to the docker file
rm -f /lib/systemd/system/systemd*udev* ; \ rm -f /lib/systemd/system/getty.target;
causes both the runnaway agetty and the spike in systemd-udevd processes to go away. I understand there is no need for udev or getty in containers.
I did also try: RUN systemctl disable getty.target RUN systemctl disable systemd-udevd.service
and although the Dockerfile built fine, all the getty and udev services were still running as they were previously. So those two "systemctl disable" appear to be no-ops. Perhaps they get run before /sbin/init (systemd) is invoked.