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

David Herrmann dh.herrmann at gmail.com
Fri Mar 20 03:08:01 PDT 2015


On Fri, Mar 20, 2015 at 11:06 AM, David Herrmann <dh.herrmann at gmail.com> wrote:
> Hi
> On Fri, Mar 20, 2015 at 7:16 AM, Peter Pause <systemd-devel at fedux.org> wrote:
>> 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?
> Gnah! If I had any idea how the automake magic with unit-files works,
> I could help you. I cannot see why the unit file is not distributed.
> Maybe Zbigniew has an idea (CC).
> For now, you can just copy it from systemd-git:
> http://cgit.freedesktop.org/systemd/systemd/plain/units/container-getty@.service.m4.in
> (you need to remove the m4_ifdef() magic, though)

Btw., the tarball seems to include the container-getty file. You need
systemd-209, though. Maybe this is an issue of your distributor, at


More information about the systemd-devel mailing list