Hello Felipe, On Tue, 2015-09-08 at 14:18 -0300, Felipe Sateler wrote: > > Please find attached the journalctl -M log. > > It looks like the gettys in both containers cannot start, but I have > no idea where to look for why. Isn't systemd supposed to disable > tty's
Actually it is the other way around. In the opensuse container, the agetty process runs active as I login into it. It literally eats up all the CPU and drains my battery. (this login is done through the systemd -nspawn interface. machinectl still cannot login, or precisely, spawn a getty.) > when running in a container? Maybe you have modified the containers > to > have 4 ttys? No. No modifications made. Initially, based on the conversation in this bug report about pam login, I thought it may have been a Debian specific oddity. But with other containers, opensuse and fedora, it seems to be a systemd problem. I have made no modifications to the containers. For whatever reasons, those containers (fedora and opensuse) has systemd .service files for 4 ttys defined. Lennart has closed the upstream bug, marking as fixed. https://github.com/systemd/systemd/issues/685 So, for now, I'm going to wait for the new release to land in Debian, and then explore again. PS: I booted the same with LXC, and have not run into the issues. Sometimes, choice is really good. :-) -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
