From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giovanni Biscuolo Subject: bug#34211: error running container: mingetty cannot find ttys Date: Tue, 12 Feb 2019 11:25:19 +0100 Message-ID: <8736otfgmo.fsf@roquette.mug.biscuolo.net> References: <874l9wbpfb.fsf@roquette.mug.biscuolo.net> <20190126192150.GD11329@macbook41> <87sgx1glhv.fsf@roquette.mug.biscuolo.net> <87zhr2q862.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:34463) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtVGO-00077s-HM for bug-guix@gnu.org; Tue, 12 Feb 2019 05:26:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtVGM-0003fB-E9 for bug-guix@gnu.org; Tue, 12 Feb 2019 05:26:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:45162) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gtVGM-0003eL-4V for bug-guix@gnu.org; Tue, 12 Feb 2019 05:26:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gtVGL-0003FW-RL for bug-guix@gnu.org; Tue, 12 Feb 2019 05:26:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87zhr2q862.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org, 34211@debbugs.gnu.org, help-guix@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Ludo' thank you for looking into this issue! Ludovic Court=C3=A8s writes: [...] > I also get this behavior. OK, so this is deterministic now :-) > 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 t= o start, and > get restarted, indefinitely. actually they do fail but they are not respawned, the services that get respawned are term-tty[1..6] > 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 = obviously has a > different PID outside the container), then you can do: > > guix container exec NNN /bin/sh I have to use "sudo" to be able to start and "guix container exec" a shell in it (I mean: sudo guix container exec...) I used that command in another terminal so I could see the console messages from the container > 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.) oh yes! I did not realized that my container was there waiting for me :-) ...I also did not realized thet the container is started as a foreground process, so we nees to background I used pstree too, we need a better way to interact with a container (by name and not by PID); sorry but I still cannot help here, my Guile proficency is still too low; anyway this is tangent to this bug > In that shell, you can do: [...] > So in that sense everything is working =E2=80=9Cas expected.=E2=80=9D yes, I see: I stopped term-tty[1..6] and the failure messages disappeared > Now, it would make more sense to simply remove those =E2=80=98console-fon= t-ttyN=E2=80=99 > services in a container and everything that depends on them. as pointed above the faining services are term-tty[1..6], console-font-tty[1..6] fails but do not get respawned do they are not the real issue > Not sure if we should do that automatically. I'll try to remove term-tty[1..6] manually from services declaration, if I manage to "manually" solve this I'll report here > Thoughts? since mingetty does not make sense in a container I'd remove term-tty[1..6] (and console-font-tty[1..6]) automatically and by default when we create a container via "guix system container..." Thanks! Giovanni =2D-=20 Giovanni Biscuolo Xelera IT Infrastructures --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEERcxjuFJYydVfNLI5030Op87MORIFAlxinxAACgkQ030Op87M ORIt9BAAgVP9H/WfUoc5byQh7CGfi79rOoLsFMUnm/QwBDrgAjHj7pqHgjVaMwfw yZpLcHYCiyI3z7vVUvzX1nunxcwQricsfBffO9NmPOxmA4c7jaiaSGx40GM1nORg hQ+r6aFD8OBfvDfxBGqGllunpGlU/+92hY5mAgqFrzkUI9pDdl0LeiXzqLOq5re0 hJMqF8z2oG4fBPCBu27/60R91w0bHGc68wC/Ht5vd+ZOYnuMj9bgoYl6AUrff5tG RlLEv3dT7sU6LdUguEZ19q1mnkFc7MU4Ll0mWma023unATr/Jw5zXWVLJZMxgkcP ynRKa4JeVnul7PGMAXkwJXxTbP+DD7dEq73IluP+4Z9U2nIcPnd9flVymMOfCAuo ixalPOKxuZjr4UdQT2Hnv4ox8lWFgkfMsZWy+tOW9iBdh8T+S6/lvs8xXMH9fCdV Hevvc/bvusvpGig87+WezwFFTOxayR5Y8hKlpWcMAHFt07qMEvhrucMgUiBQ+pWQ mdbesEyrs+y36zBJ8Zn+uW7QfzGDS/D80d6Z1ilvNRVD+NmqZ19ZUp0eyl5RQR7P TDvjRFmrlLu124hcIuWl0wIjXSuwt72EynDGohx6PQKE0ZlX13QXA7WbbYUNj8iz f/SdXvtNcyx9yj/btbsLUc2ODQS1E2YD2QvQL43mmoz/tG78IcU= =x/A1 -----END PGP SIGNATURE----- --=-=-=--