Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-09-15 Thread Ritesh Raj Sarraf
On Tue, 2015-09-15 at 05:18 +0200, Michael Biebl wrote: > How exactly did you start the containers? `machinectl start container_name` > Does it work, if you copy them to /var/lib/machines/ and > start them via > systemctl start systemd-nspawn@.service ? > Yes. systemd-nspawn booted it proper.

Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-09-14 Thread Michael Biebl
How exactly did you start the containers? Does it work, if you copy them to /var/lib/machines/ and start them via systemctl start systemd-nspawn@.service ? At least this works for me. signature.asc Description: OpenPGP digital signature ___

Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-09-09 Thread Ritesh Raj Sarraf
On Tue, 2015-09-08 at 19:34 +0200, Michael Biebl wrote: > Have you added /dev/pts/0 to /etc/securetty? > That's currently necessary in Debian. > Also, installing dbus inside the container is mandatory as well. Yes. That was the conclusion we made in the last conversation from July. -- Ritesh

Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-09-08 Thread Michael Biebl
Am 08.09.2015 um 19:18 schrieb Felipe Sateler: > Hi Ritesh, > > On 4 September 2015 at 04:18, Ritesh Raj Sarraf wrote: >> Package: systemd >> Version: 225-1 >> Followup-For: Bug #792882 >> >> Please find attached the journalctl -M log. > > It looks like the gettys in both

Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-09-08 Thread Ritesh Raj Sarraf
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

Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-09-08 Thread Felipe Sateler
Hi Ritesh, On 4 September 2015 at 04:18, Ritesh Raj Sarraf wrote: > Package: systemd > Version: 225-1 > Followup-For: Bug #792882 > > 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.

Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-07-23 Thread Michael Biebl
Control: merge 771675 -1 This turned out to be the same issue as #771675: missing dbus in the container and missing pts/0 in /etc/securetty Merging the two bug reports. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-07-23 Thread Michael Biebl
Control: tags -1 = upstream Control: severity -1 normal Hi! Am 19.07.2015 um 18:54 schrieb Ritesh Raj Sarraf: Package: systemd Version: 222-2 Severity: important File: /bin/machinectl Tags: patch I am evaluating moving from LXC to systemd-nspawn. During the course, I've run into the

Processed: Re: Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-07-23 Thread Debian Bug Tracking System
Processing control commands: forwarded -1 https://github.com/systemd/systemd/issues/685 Bug #792882 [systemd] /bin/machinectl: machinectl fails to login to container Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/685'. -- 792882:

Bug#792882: /bin/machinectl: machinectl fails to login to container

2015-07-23 Thread Ritesh Raj Sarraf
I've filed the bug upstream at: https://github.com/systemd/systemd/issues/685 On Thu, Jul 23, 2015 at 5:22 PM, Michael Biebl bi...@debian.org wrote: Am 23.07.2015 um 13:48 schrieb Michael Biebl: I am evaluating moving from LXC to systemd-nspawn. During the course, I've run into the following