From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: bug#34211: error running container: mingetty cannot find ttys Date: Mon, 11 Feb 2019 23:20:21 +0100 Message-ID: <87zhr2q862.fsf@gnu.org> References: <874l9wbpfb.fsf@roquette.mug.biscuolo.net> <20190126192150.GD11329@macbook41> <87sgx1glhv.fsf@roquette.mug.biscuolo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <87sgx1glhv.fsf@roquette.mug.biscuolo.net> (Giovanni Biscuolo's message of "Wed, 06 Feb 2019 13:16:44 +0100") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Giovanni Biscuolo Cc: guix-devel@gnu.org, help-guix@gnu.org, 34211@debbugs.gnu.org List-Id: guix-devel.gnu.org Hi Giovanni, Giovanni Biscuolo skribis: > plase is there someone else that could reproduce this issue with "guix > system container": https://issues.guix.info/issue/34211 ? [...] > Feb 6 12:45:44 localhost /gnu/store/mbq93mr1vbs6za0n0yn32gfsyq1wx6xf-min= getty-1.08/sbin/mingetty[217]: tty5: No such file or directory > Feb 6 12:45:44 localhost /gnu/store/mbq93mr1vbs6za0n0yn32gfsyq1wx6xf-min= getty-1.08/sbin/mingetty[216]: tty6: No such file or directory > Feb 6 12:45:44 localhost /gnu/store/mbq93mr1vbs6za0n0yn32gfsyq1wx6xf-min= getty-1.08/sbin/mingetty[218]: tty3: No such file or directory > Feb 6 12:45:44 localhost /gnu/store/mbq93mr1vbs6za0n0yn32gfsyq1wx6xf-min= getty-1.08/sbin/mingetty[219]: tty2: No such file or directory > Feb 6 12:45:44 localhost /gnu/store/mbq93mr1vbs6za0n0yn32gfsyq1wx6xf-min= getty-1.08/sbin/mingetty[220]: tty1: No such file or directory > > I have to TERM the the container since the "ttN: No such file or > directory" message loops indefinitely I also get this behavior. What happens is that the /dev/ttyN nodes do not exist (understandably), and thus the =E2=80=98console-font-ttyN=E2=80=99 Shepherd services fail to = start, and get restarted, indefinitely. The container is working as expected though. If you find the PID of the container=E2=80=99s =E2=80=98shepherd=E2=80=99 process (its PID 1, which ob= viously has a different PID outside the container), then you can do: guix container exec NNN /bin/sh where NNN is that PID of that =E2=80=98shepherd=E2=80=99 process (I use =E2= =80=98pstree=E2=80=99 to find the PID=E2=80=A6 not very convenient.) In that shell, you can do: --8<---------------cut here---------------start------------->8--- sh-4.4# . /etc/profile=20=20=20=20=20=20=20=20=20 sh-4.4# ls bin dev etc gnu home proc root run sys tmp var sh-4.4# herd status Started: + containerized-shepherd + file-systems + guix-daemon + host-name + loopback + nscd + root + root-file-system + ssh-daemon + syslogd + term-tty1 + term-tty2 + term-tty3 + term-tty4 + term-tty5 + term-tty6 + udev + urandom-seed + user-file-systems + user-processes + virtual-terminal Stopped: - console-font-tty1 - console-font-tty2 - console-font-tty3 - console-font-tty4 - console-font-tty5 - console-font-tty6 - networking - term-auto - user-homes --8<---------------cut here---------------end--------------->8--- So in that sense everything is working =E2=80=9Cas expected.=E2=80=9D Now, it would make more sense to simply remove those =E2=80=98console-font-= ttyN=E2=80=99 services in a container and everything that depends on them. Not sure if we should do that automatically. Thoughts? Thanks, Ludo=E2=80=99.