[systemd-devel] Nspawn / getty restart loop
meechman at gmail.com
Mon Dec 8 06:29:43 PST 2014
I created a fresh container by following the steps here
https://wiki.archlinux.org/index.php/Arch_systemd_container using the
pacstrap -i -c -d ~/MyContainer base
Not sure what is pulling it in. Nor how to find out.
If I start it via systemd, the journal is quiet until I log in (via
machinectl login) for the very first time. Then after I logout the
service goes into a restart loop every 10 seconds.
On Mon, Dec 8, 2014 at 9:15 AM, Lennart Poettering <lennart at poettering.net>
> On Sun, 07.12.14 09:20, Meech (meechman at gmail.com) wrote:
> > Disabling seems to have no effect, it's a static service:
> > console-getty.service disabled
> > container-getty at .service static
> > getty at .service enabled
> > serial-getty at .service disabled
> Well, something appears to pull it in, the question is what precisely
> is it...
> > However, I think adding this to the [unit] section seems to help:
> > ConditionPathExists=/dev/pts/%I
> > Still testing. Thanks.
> That'd just be a work-around to ensure the service is skipped when it
> is pulled in incorrectly, but we really should figure out why it is
> pulled in incorrectly in the first place, and fix that.
> Lennart Poettering, Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the systemd-devel