alpine 3.4 LXC/LXD container getty error

3 posts / 0 new
Last post
#1 Sat, 2016-07-23 13:54
melato
  • melato's picture
  • Offline
  • Last seen: 1 year 8 months ago
  • Joined: 2016-07-23

In a fresh LXD Alpine 3.4 container, I see the following 8 messages repeat once per second in /var/log/messages:
daemon.info init: process '/sbin/getty 38400 tty1' (pid 485) exited. Scheduling for restart.
daemon.info init: process '/sbin/getty 38400 tty2' (pid 486) exited. Scheduling for restart.
daemon.info init: process '/sbin/getty 38400 tty3' (pid 487) exited. Scheduling for restart.
daemon.info init: process '/sbin/getty 38400 tty4' (pid 488) exited. Scheduling for restart.
daemon.info init: can't open /dev/tty1: No such file or directory
daemon.info init: can't open /dev/tty2: No such file or directory
daemon.info init: can't open /dev/tty3: No such file or directory
daemon.info init: can't open /dev/tty4: No such file or directory

Steps to Reproduce:
On an Ubuntu 16.04 host, create an Alpine 3.4 LXD container:
sudo lxc launch images:alpine/3.4/amd64 alpine34

sudo lxc exec alpine34 sh
# tail -f /var/log/messages

Should I enter this in the bug database?

As a workaround, I commented out the 4 /sbin/getty lines form /etc/inittab and rebooted the container.

The LXC console doesn't seem to hurt:
# Main LXC console console
::respawn:/sbin/getty 38400 console

But I don't think I need it, so I commented it too. The LXD container can be used without it.

Sat, 2016-07-23 18:03
melato
  • melato's picture
  • Offline
  • Last seen: 1 year 8 months ago
  • Joined: 2016-07-23

I entered an LXC issue for this: https://github.com/lxc/lxc/issues/1096
I don't really know why the ttys are in /etc/inittab in the first place.

Sun, 2016-07-24 14:55
melato
  • melato's picture
  • Offline
  • Last seen: 1 year 8 months ago
  • Joined: 2016-07-23
Log in or register to post comments