Devuan bug report logs - #440
util-linux: /sbin/getty does not allow login from systemd-nspawn

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

Package: util-linux
Version: 2.33.1-0.1+devuan1~beowulf2
Severity: normal

Dear Maintainer,

I made a Devuan container on Debian Bullseye by
mmdebstrap --components="main contrib non-free" --variant=standard beowulf /var/lib/lxc/devuan/rootfs http://deb.devuan.org/merged

Then I commented-in the last line in /etc/inittab of Devuan as

# Example for systemd-nspawn
# Only /dev/console exists inside nspawn, so we need a getty on that.
# Also make sure to comment out the gettys on tty* above.
C0:2345:respawn:/sbin/getty -8 --noclear --keep-baud console 115200,38400,9600

"lxc-start -F -n devuan" works fine and it allows login.
On the other hand, when the Devuan container is started by
"systemd-nspawn -D /var/lib/lxc/devuan/rootfs -b",
typing "root" to "login: " just says "Login incorrect" without asking password.

Best regards, Ryutaroh Matsumoto

-- System Information:
Architecture: x86_64

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages util-linux depends on:
ii  fdisk          2.33.1-0.1+devuan1~beowulf2
ii  libaudit1      1:2.8.4-3
ii  libblkid1      2.33.1-0.1+devuan1~beowulf2
ii  libc6          2.28-10
ii  libcap-ng0     0.7.9-2
ii  libeudev1      3.2.7-6
ii  libmount1      2.33.1-0.1+devuan1~beowulf2
ii  libpam0g       1.3.1-5
ii  libselinux1    2.8-1+b1
ii  libsmartcols1  2.33.1-0.1+devuan1~beowulf2
ii  libtinfo6      6.1+20181013-2+deb10u2
ii  libuuid1       2.33.1-0.1+devuan1~beowulf2
ii  login          1:4.5-1.1
ii  zlib1g         1:1.2.11.dfsg-1

util-linux recommends no packages.

Versions of packages util-linux suggests:
pn  dosfstools           <none>
pn  kbd | console-tools  <none>
pn  util-linux-locales   <none>

-- no debconf information

Message #8 received at 440@bugs.devuan.org (full text, mbox, reply):

Ryutaroh,

On Fri, 08 May 2020 16:16:20 +0900 (JST) Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> wrote:
> Package: util-linux
> Version: 2.33.1-0.1+devuan1~beowulf2
> Severity: normal
> 
> Dear Maintainer,
> 
> I made a Devuan container on Debian Bullseye by
> mmdebstrap --components="main contrib non-free" --variant=standard beowulf /var/lib/lxc/devuan/rootfs http://deb.devuan.org/merged
> 
> Then I commented-in the last line in /etc/inittab of Devuan as


> # Example for systemd-nspawn
> # Only /dev/console exists inside nspawn, so we need a getty on that.
> # Also make sure to comment out the gettys on tty* above.

Did you also comment out the previous tty* gettys as indicated^^^

Mark

Message #13 received at 440@bugs.devuan.org (full text, mbox, reply):

Hi Mark,
Thanks again for your response.

> Did you also comment out the previous tty* gettys as indicated^^^

I forgot doing it, but commenting out

1:2345:respawn:/sbin/getty 38400 tty1
...
6:23:respawn:/sbin/getty 38400 tty6

does not change the symptom.

By the way, very few people on the earth expect friendly relationship
between Devuan and systemd, and Devuan Beowulf works (almost) fine
under LXC containers, so I have no objection if this bug receives "wontfix" tag :-)

You can just tell people to use LXC...

Best regards, Ryutaroh

Message #16 received at 440@bugs.devuan.org (full text, mbox, reply):

On Fri, May 08, 2020 at 04:16:20PM +0900, Ryutaroh Matsumoto wrote:
> Package: util-linux
> Version: 2.33.1-0.1+devuan1~beowulf2
> Severity: normal
> 
> Dear Maintainer,
> 
> I made a Devuan container on Debian Bullseye by
> mmdebstrap --components="main contrib non-free" --variant=standard beowulf /var/lib/lxc/devuan/rootfs http://deb.devuan.org/merged
> 
> Then I commented-in the last line in /etc/inittab of Devuan as
> 
> # Example for systemd-nspawn
> # Only /dev/console exists inside nspawn, so we need a getty on that.
> # Also make sure to comment out the gettys on tty* above.
> C0:2345:respawn:/sbin/getty -8 --noclear --keep-baud console 115200,38400,9600
> 
> "lxc-start -F -n devuan" works fine and it allows login.
> On the other hand, when the Devuan container is started by
> "systemd-nspawn -D /var/lib/lxc/devuan/rootfs -b",
> typing "root" to "login: " just says "Login incorrect" without asking password.

Thinking about this more, that sounds like a baud rate issue.

Does using a simpler/different line in inittab help?

 C0::respawn:/sbin/getty 38400 console

Is about as simple as you can go, I suppose.

Mark

Message #21 received at 440@bugs.devuan.org (full text, mbox, reply):

> Thinking about this more, that sounds like a baud rate issue.
> Does using a simpler/different line in inittab help?
>  C0::respawn:/sbin/getty 38400 console
> Is about as simple as you can go, I suppose.

Umm, it does not work, the same symptom...

Ryutaroh

Send a report that this bug log contains spam.