[systemd-devel] machinectl login <system>: Failed to get machine PTY: Unit container-getty at 0.service failed to load: No such file or directory.

Peter Pause systemd-devel at fedux.org
Thu Mar 19 23:16:01 PDT 2015


Excerpts from David Herrmann's message of 2015-03-19 14:44:54 +0100:
> 
> The file container-getty at .service is available in your container?

Using a simple find, "failed":

[root at 746b0d570b72 /]# find / -name  container-getty at .service

It's not even part of the systemd package coming with Centos 7

[root at 746b0d570b72 /]# rpm -ql systemd | grep getty
/usr/lib/systemd/system-generators/systemd-getty-generator
/usr/lib/systemd/system/console-getty.service
/usr/lib/systemd/system/getty.target
/usr/lib/systemd/system/getty at .service
/usr/lib/systemd/system/multi-user.target.wants/getty.target
/usr/lib/systemd/system/serial-getty at .service
/usr/share/man/man8/systemd-getty-generator.8.gz

What was the first version of systemd which shiped this file?

Does it make sense to add a section to the manual making users aware of
this requirement?

> /sbin/agetty is available in your container?
Yes.

[root at 746b0d570b72 /]# ls -al /usr/sbin/agetty
-rwxr-xr-x 1 root root 36840 Jun 17  2014 /usr/sbin/agetty
> 
> Thanks
> David
> 



More information about the systemd-devel mailing list